[12:13] <parlos> Good morning, i have a question about MAAS networking and Landscape/Autopilot.
[12:17] <parlos> The nodes boots from the private network and are commissioned. The private network is detected to one fabric, and for some nodes the public is also correctly detected on another fabric. I make sure that the private subnet is selected correctly,
[12:19] <parlos> and for the nodes with public network their interface is connected to the correct fabric and I select the public subnet, but make sure not to config the IP assignment (unconfigured option).
[12:20] <parlos> at this point Landscape/Openstack the OpenvSwitch does not detect any Public Network, the drop down is empty.
[12:21] <parlos> If I remove the public subnet from the one node with connection to it, then Landscape/Openstack open vSwitch puts the private network in the dropdown.. . any ideas?
[14:55] <parlos> Have a nice day
[15:13] <mup> Bug #1714533 opened: Can't auto-enlist HP Moonshot m400 <MAAS:New> <https://launchpad.net/bugs/1714533>
[15:13] <mup> Bug #1714535 opened: Unavailable bootloader needs better error messages <MAAS:New> <https://launchpad.net/bugs/1714535>
[15:16] <mup> Bug #1714533 changed: Can't auto-enlist HP Moonshot m400 <MAAS:New> <https://launchpad.net/bugs/1714533>
[15:16] <mup> Bug #1714535 changed: Unavailable bootloader needs better error messages <MAAS:New> <https://launchpad.net/bugs/1714535>
[15:22] <mup> Bug #1714533 opened: Can't auto-enlist HP Moonshot m400 <MAAS:New> <https://launchpad.net/bugs/1714533>
[15:22] <mup> Bug #1714535 opened: Unavailable bootloader needs better error messages <MAAS:New> <https://launchpad.net/bugs/1714535>
[19:43] <mup> Bug #1714580 opened: [2.3, trunk] Running old format test script results in it being reported as failed (even if suceeded) <hardware-testing> <testing> <MAAS:Triaged> <https://launchpad.net/bugs/1714580>