[01:29] <mup> Bug #1769009 opened: Unable to deploy Precise with Bionic with ext4 filesystem <MAAS:New> <https://launchpad.net/bugs/1769009>
[09:13] <mup> Bug #1769099 opened: [2.4, UI, regression] Deploy action shows options twice <MAAS:Triaged> <https://launchpad.net/bugs/1769099>
[11:52] <mup> Bug #1769123 opened: [2.4b3] web UI link error goes to old nodes page <MAAS:New> <https://launchpad.net/bugs/1769123>
[12:56] <mup> Bug #1481261 changed: MAC address text field on Power section accepts wrong format <power> <ui> <MAAS:Fix Released by ricgard> <https://launchpad.net/bugs/1481261>
[13:29] <mup> Bug #1683769 changed: [2.2.0rc2, UX Improvement] In the device details page, the take action dropdpwn button is not needed <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1683769>
[13:29] <mup> Bug #1722910 changed: [2.3b1] In Devices->Interfaces when the focus is int he MAC address the Enter key opens the menu of the previous row <ui> <MAAS:Triaged by deadlight> <https://launchpad.net/bugs/1722910>
[13:45] <mup> Bug #1769139 opened: package maas-region-controller 2.4.0~beta2-6865-gec43e47e6-0ubuntu1 failed to install/upgrade: installed maas-region-controller package post-installation script subprocess returned error exit status 1 <apport-package> <bionic> <i386> <need-duplicate-check> <maas
[13:45] <mup> (Ubuntu):Incomplete> <https://launchpad.net/bugs/1769139>
[14:05] <mup> Bug #1730972 changed: [2.3qa, UI] When the contextual menu is open and I scroll down the menu is still open and sits on top of the header <2.3qa> <ui> <ui-papercut> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1730972>
[14:05] <mup> Bug #1731191 changed: [2.3rc2, UI] The padding of the icons in hardware testing is not right <2.3qa> <ui> <ui-papercut> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1731191>
[14:05] <mup> Bug #1731210 changed: [2.3rc2, UI] The padding of the metrics/ error text in the expanded hardware testing row is smaller than guidelines <2.3qa> <ui> <ui-papercut> <MAAS:Invalid by deadlight> <https://launchpad.net/bugs/1731210>
[14:08] <mup> Bug #1730972 opened: [2.3qa, UI] When the contextual menu is open and I scroll down the menu is still open and sits on top of the header <2.3qa> <ui> <ui-papercut> <MAAS:Fix Committed by deadlight> <https://launchpad.net/bugs/1730972>
[14:08] <mup> Bug #1731191 opened: [2.3rc2, UI] The padding of the icons in hardware testing is not right <2.3qa> <ui> <ui-papercut> <MAAS:Fix Committed by deadlight> <https://launchpad.net/bugs/1731191>
[14:15] <mup> Bug #1769144 opened: Unable to commission node, ends up in an endless reboot cycle <maas (Ubuntu):New> <https://launchpad.net/bugs/1769144>
[17:10] <sigma_> hi, i have a problem with maas.   Error: Mount the root '/' filesystem to be able to deploy this node. this is the error message i get when i have rebooted a laptop. it downloads the kernel and the initrd, boots, does a bunch of stuff real quick. then it just shuts down
[17:10] <sigma_> any idea what could be wrong?
[19:11] <ltrager> sigma_: Look on the storage tab on the machine that isn't deploying. '/' needs to be defined there. If it isn't defined you can either configure yourself or recommission the machine to get the default settings
[19:27] <KingJ> Hmm, running in to a storage setup issue I can't work out. I've got 1x 120GB SSD and 2x 500GB HDD in a comissioned server. I've created a MD RAID1 across the two 500GB disks, and on that created a 1GB fat32 partition on /boot and 499GB partition used for bcache.
[19:28] <KingJ> However, MAAS is erroring with: "Error: This node cannot be deployed because it cannot boot from a bcache volume. Mount /boot on a non-bcache device to be able to deploy this node."
[19:29] <KingJ> Which well, doesn't seem to match up with what i've defined: https://i.imgur.com/2C282gG.jpg
[19:33] <KingJ> The error goes away though if create a /boot partition on one of the physical disks instead of md0 though
[19:47] <luckielordie> hi guys, I'm having trouble configuring a Pod
[19:47] <luckielordie> can anyone help me?
[19:48] <luckielordie> I'm getting " Add pod Name  Pod type  Virsh address  Virsh password (optional)      Failed talking to pod: Failed to login to virsh console" When I try to create the Pod
[19:49] <luckielordie> I can still run the command to list the virsh machines remotely and it works fine