[08:23] <mup> Bug #1908052 changed: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa <MAAS:Invalid> <Stress-ng:New> <https://launchpad.net/bugs/1908052>
[08:29] <mup> Bug #1908052 opened: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa <MAAS:Invalid> <Stress-ng:New> <https://launchpad.net/bugs/1908052>
[08:32] <mup> Bug #1908052 changed: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa <MAAS:Invalid> <Stress-ng:New> <https://launchpad.net/bugs/1908052>
[08:53] <mup> Bug #1910411 changed: No reason visible in Web UI when a commissioning step fails in the central processing by regiond <ps5> <MAAS:New> <https://launchpad.net/bugs/1910411>
[09:08] <mup> Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem <curtin:Invalid> <maas-images:New> <https://launchpad.net/bugs/1882798>
[09:08] <mup> Bug #1888719 changed: Improve migration of rack controllers <MAAS:Invalid> <https://launchpad.net/bugs/1888719>
[09:11] <mup> Bug #1882798 opened: Can't deploy CentOS 6 with xfs filesystem <curtin:Invalid> <maas-images:New> <https://launchpad.net/bugs/1882798>
[09:11] <mup> Bug #1888719 opened: Improve migration of rack controllers <MAAS:Invalid> <https://launchpad.net/bugs/1888719>
[09:15] <mup> Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem <curtin:Invalid> <maas-images:New> <https://launchpad.net/bugs/1882798>
[09:15] <mup> Bug #1888719 changed: Improve migration of rack controllers <MAAS:Invalid> <https://launchpad.net/bugs/1888719>
[09:18] <mup> Bug #1882798 opened: Can't deploy CentOS 6 with xfs filesystem <curtin:Invalid> <maas-images:New> <https://launchpad.net/bugs/1882798>
[09:18] <mup> Bug #1888719 opened: Improve migration of rack controllers <MAAS:Invalid> <https://launchpad.net/bugs/1888719>
[09:24] <mup> Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem <curtin:Invalid> <maas-images:New> <https://launchpad.net/bugs/1882798>
[09:24] <mup> Bug #1888719 changed: Improve migration of rack controllers <MAAS:Invalid> <https://launchpad.net/bugs/1888719>
[11:15] <mup> Bug #1789650 changed: Servers set to boot from disk after MAAS installation <hwcert-server> <curtin:Fix Committed by raharper> <MAAS:Fix Released> <https://launchpad.net/bugs/1789650>
[13:26] <parlos> Good day MAAS!
[13:37] <parlos> I've have a problem. I added a rackd to my already existing region+rackd, maas (3.0.0~rc1). It seemed fine. But when I tried to do an deployment, co juju, thing got strange. Instead of deploying 1 host, maas tried to deploy 3 hosts. + Juju complained that i could not access the maas api.
[13:37] <parlos> I then disabled the deployment, and removed the new rackd.
[13:45] <parlos> Now to the problem, at this time, it seems that the dhcpd isnt answering requests anymore. ..
[13:48] <parlos> My maas deployment is the snap version. Its all green in the UI, but no requests are handled (verified via tcpdump).
[14:34] <mup> Bug #1882911 changed: Failure to update pod with error cascade attempting to talk to virsh <MAAS:Fix Committed> <https://launchpad.net/bugs/1882911>
[14:40] <mup> Bug #1882911 opened: Failure to update pod with error cascade attempting to talk to virsh <MAAS:Fix Committed> <https://launchpad.net/bugs/1882911>
[14:46] <mup> Bug #1882911 changed: Failure to update pod with error cascade attempting to talk to virsh <MAAS:Fix Committed> <https://launchpad.net/bugs/1882911>