=== arif-ali_ is now known as arif-ali [08:23] Bug #1908052 changed: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa [08:29] Bug #1908052 opened: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa [08:32] Bug #1908052 changed: HW test stress-ng-cpu-long timeout, page allocation failure in stress-ng-numa [08:53] Bug #1910411 changed: No reason visible in Web UI when a commissioning step fails in the central processing by regiond [09:08] Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem [09:08] Bug #1888719 changed: Improve migration of rack controllers [09:11] Bug #1882798 opened: Can't deploy CentOS 6 with xfs filesystem [09:11] Bug #1888719 opened: Improve migration of rack controllers [09:15] Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem [09:15] Bug #1888719 changed: Improve migration of rack controllers [09:18] Bug #1882798 opened: Can't deploy CentOS 6 with xfs filesystem [09:18] Bug #1888719 opened: Improve migration of rack controllers [09:24] Bug #1882798 changed: Can't deploy CentOS 6 with xfs filesystem [09:24] Bug #1888719 changed: Improve migration of rack controllers [11:15] Bug #1789650 changed: Servers set to boot from disk after MAAS installation [13:26] Good day MAAS! [13:37] 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] I then disabled the deployment, and removed the new rackd. [13:45] Now to the problem, at this time, it seems that the dhcpd isnt answering requests anymore. .. [13:48] My maas deployment is the snap version. Its all green in the UI, but no requests are handled (verified via tcpdump). [14:34] Bug #1882911 changed: Failure to update pod with error cascade attempting to talk to virsh [14:40] Bug #1882911 opened: Failure to update pod with error cascade attempting to talk to virsh [14:46] Bug #1882911 changed: Failure to update pod with error cascade attempting to talk to virsh