[00:07] <mup> Bug #1497480 opened: curtin userdata fails if 'kernel' entry lacks 'mapping' key <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1497480>
[00:40] <mup> Bug #1497480 changed: curtin userdata fails if 'kernel' entry lacks 'mapping' key <canonical-bootstack> <curtin:New> <https://launchpad.net/bugs/1497480>
[00:58] <mup> Bug #1482589 changed: test_size_is_rounded_to_next_block is flaky <MAAS:Invalid> <https://launchpad.net/bugs/1482589>
[01:01] <mup> Bug #1482589 opened: test_size_is_rounded_to_next_block is flaky <MAAS:Invalid> <https://launchpad.net/bugs/1482589>
[01:04] <mup> Bug #1482589 changed: test_size_is_rounded_to_next_block is flaky <MAAS:Invalid> <https://launchpad.net/bugs/1482589>
[02:35] <mup> Bug #1464281 changed: 1.8rc3: Incorrect IP Address label in UI (dynamic) under Network->IP for previous static IP address. Deployment gets static IP <oil> <MAAS:Invalid> <MAAS 1.8:Won't Fix> <https://launchpad.net/bugs/1464281>
[02:41] <mup> Bug #1464281 opened: 1.8rc3: Incorrect IP Address label in UI (dynamic) under Network->IP for previous static IP address. Deployment gets static IP <oil> <MAAS:Invalid> <MAAS 1.8:Won't Fix> <https://launchpad.net/bugs/1464281>
[02:44] <mup> Bug #1464281 changed: 1.8rc3: Incorrect IP Address label in UI (dynamic) under Network->IP for previous static IP address. Deployment gets static IP <oil> <MAAS:Invalid> <MAAS 1.8:Won't Fix> <https://launchpad.net/bugs/1464281>
[02:53] <mup> Bug #1464281 opened: 1.8rc3: Incorrect IP Address label in UI (dynamic) under Network->IP for previous static IP address. Deployment gets static IP <oil> <MAAS:Invalid> <MAAS 1.8:Won't Fix> <https://launchpad.net/bugs/1464281>
[02:59] <mup> Bug #1464281 changed: 1.8rc3: Incorrect IP Address label in UI (dynamic) under Network->IP for previous static IP address. Deployment gets static IP <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1464281>
[02:59] <mup> Bug #1469874 changed: MAAS 1.8 not allowed to edit node details in gui after upgrade <maas> <maas-gui> <MAAS:Invalid> <https://launchpad.net/bugs/1469874>
[07:50] <nburtsev> Hello. Anyone knows if code that automatically detects nodegroup for node during enlistment is broken?
[07:52] <nburtsev> because it tries to find a nodegroup from ip address of whever enlistment request came from, which supposedly is (or was) cluster controller, but it actually has 127.0.0.1 in that field