[14:40] <mup> Bug #1747928 opened: When a known server in Deploying state boots to the enlisting environment, it should not just power off. <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1747928>
[14:43] <mup> Bug #1747928 changed: When a known server in Deploying state boots to the enlisting environment, it should not just power off. <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Opinion> <https://launchpad.net/bugs/1747928>
[14:46] <mup> Bug #1747930 opened: MAAS should recognize servers that are Powered Off in Deploying state, and do something about it. <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1747930>
[14:52] <mup> Bug #1747928 opened: When a known server in Deploying state boots to the enlisting environment, it should not just power off. <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1747928>
[15:01] <mup> Bug #1747930 changed: MAAS should recognize servers that are Powered Off in Deploying state, and do something about it. <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Opinion> <https://launchpad.net/bugs/1747930>
[15:16] <mup> Bug #1747930 opened: MAAS should recognize servers that are Powered Off in Deploying state, and do something about it. <cdo-qa> <foundations-engine> <MAAS:Opinion> <https://launchpad.net/bugs/1747930>
[15:25] <mup> Bug #1747928 changed: When a known server in Deploying state boots to the enlisting environment, it should not just power off. <cdo-qa> <foundations-engine> <MAAS:Opinion> <https://launchpad.net/bugs/1747928>
[15:25] <mup> Bug #1747930 changed: MAAS should recognize servers that are Powered Off in Deploying state, and do something about it. <cdo-qa> <foundations-engine> <MAAS:Opinion> <https://launchpad.net/bugs/1747930>
[16:32] <mup> Bug #1747928 opened: When a known server in Deploying state boots to the enlisting environment, it should not just power off. <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1747928>
[20:42] <mup> Bug #1748010 opened: "Unconfigured" interface in MAAS becomes DHCP interface on deployed node <MAAS:New> <https://launchpad.net/bugs/1748010>
[22:33] <mup> Bug #1748031 opened: [2.4, devel]  Dashboard/Discovery page: builtins.IndexError: list index out of range <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1748031>
[22:39] <mup> Bug #1748031 changed: [2.4, devel]  Dashboard/Discovery page: builtins.IndexError: list index out of range <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1748031>
[22:42] <mup> Bug #1748031 opened: [2.4, devel]  Dashboard/Discovery page: builtins.IndexError: list index out of range <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1748031>
[22:42] <mup> Bug #1748034 opened: [2.4, devel] Node failed to be commissioned, because of the following error: ScriptSet matching query does not exist. <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1748034>
[22:48] <mup> Bug #1748034 changed: [2.4, devel] Node failed to be commissioned, because of the following error: ScriptSet matching query does not exist. <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1748034>
[23:03] <mup> Bug #1748034 opened: [2.4, devel] Node failed to be commissioned, because of the following error: ScriptSet matching query does not exist. <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1748034>
[23:45] <mup> Bug #1748031 changed: [2.4, devel]  Dashboard/Discovery page: builtins.IndexError: list index out of range <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1748031>
[23:45] <mup> Bug #1655447 opened: IEEE indexes in netaddr package may not match data in ieee-data package <MAAS:Triaged by mpontillo> <MAAS 2.3:New> <python-netaddr (Ubuntu):Confirmed> <https://launchpad.net/bugs/1655447>