[17:38] <ahasenack> continuing from my question yesterday,
[17:39] <ahasenack> I think this is the problem
[17:39] <ahasenack> (my debug)
[17:39] <ahasenack> 2018-01-13 17:38:38 maasserver: [error] Returning preseed_context={'syslog_host_port': '127.0.0.1:514', 'osystem': '', 'metadata_enlist_url': 'http://127.0.0.1/MAAS/metadata/enlist', 'server_url': 'http://127.0.0.1/MAAS/api/2.0/machines/', 'release': '', 'server_host': '127.0.0.1'}
[17:39] <ahasenack> it's telling the node to use 127.0.0.1
[18:18] <ahasenack> ok, interesting
[18:18] <ahasenack> if I fetch the preseed via this url:
[18:18] <ahasenack> http://10.0.5.5/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
[18:18] <ahasenack> it returns
[18:18] <ahasenack>     metadata_url: http://127.0.0.1:5240/MAAS/metadata/enlist
[18:18] <ahasenack> but if I fetch it via THIS url:
[18:18] <ahasenack> http://10.0.5.5:5240/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
[18:18] <ahasenack> then it returns:
[18:18] <ahasenack>     metadata_url: http://10.0.5.5:5240/MAAS/metadata/enlist
[18:19] <ahasenack> it's probably because apache is being a proxy and redirecting the former to localhost:5240
[18:19] <ahasenack> and that's where the localhost comes from
[18:19] <ahasenack> in the response
[18:48] <mup> Bug #1743142 opened: [2.3] get_enlist_preseed returns 127.0.0.1 for metadata_url <MAAS:New> <https://launchpad.net/bugs/1743142>
[19:33] <mup> Bug #1743144 opened: hpvsa-update ppa has no xenial packages <MAAS:New> <https://launchpad.net/bugs/1743144>
[22:12] <torontoyes> Can someone provide the clear steps in creating windows image that will work for MAAS, as I'm having difficulty finding that information.