[01:36] <Guest19547> Hi all, I have a question.
[01:36] <Guest19547> I login MAAS first time, but the page is blank.
[01:37] <Guest19547> Create a new user can login successfully, but I want to know why.
[02:05] <mup> Bug #1760744 opened: An error occurs when MAAS deploy Ubuntu 16.04.4 under UEFI mode on SystemX 3650 M5 <MAAS:New> <https://launchpad.net/bugs/1760744>
[04:17] <mup> Bug #1737346 changed: IPv4 and IPv6 spaces (v4 & v6 multi-homing): handling IPv4 and IPv6 subnets on the same VLAN <cpe-onsite> <juju:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1737346>
[05:39] <mup> Bug #1760770 opened: [2.4, websockets] Pod details should only load machines from pod <performance> <MAAS:In Progress by ltrager> <https://launchpad.net/bugs/1760770>
[09:27] <cnf> hi, does anyone use juju with maas pods? trying to figure out how you define the amount of disk space a pod should have
[13:16] <mup> Bug #1760860 opened: Removing mounted filesystems prompts two confusing questions <MAAS:New> <https://launchpad.net/bugs/1760860>
[13:52] <mup> Bug #1760862 opened: Support names in addition to IDs for resource pools and groups APIs <MAAS:New> <https://launchpad.net/bugs/1760862>
[14:19] <mup> Bug #1760879 opened: zfsroot fails: FileNotFoundError - [Errno 2] No such file or directory: '/dev/disk/by-id' <MAAS:New> <https://launchpad.net/bugs/1760879>
[14:22] <mup> Bug #1760880 opened: vdb partitioned with zfsroot, but not mounted: deploy failed <MAAS:New> <https://launchpad.net/bugs/1760880>
[14:46] <mup> Bug #1760888 opened: ext4 on vda, zfsroot on vdb fails <MAAS:New> <https://launchpad.net/bugs/1760888>
[14:52] <mup> Bug #1760888 changed: ext4 on vda, zfsroot on vdb fails <MAAS:New> <https://launchpad.net/bugs/1760888>
[16:01] <mup> Bug #1760919 opened: If a disk doesn't support SMART, the test shouldn't pass <MAAS:New> <https://launchpad.net/bugs/1760919>
[16:16] <mup> Bug #1760919 changed: [enhancement] If a disk doesn't support SMART, the test shouldn't pass <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1760919>
[16:19] <mup> Bug #1760919 opened: [enhancement] If a disk doesn't support SMART, the test shouldn't pass <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1760919>
[17:07] <mup> Bug #1706461 changed: Allow turning off auto-create-on-allocate for pods <cdo-qa> <internal> <pod> <MAAS:Won't Fix> <https://launchpad.net/bugs/1706461>
[18:07] <mup> Bug #1754493 opened: [2.4,b1] images never finish syncing to rack controller <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1754493>
[18:17] <mup> Bug #1754493 changed: [2.4,b1] images never finish syncing to rack controller <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1754493>
[18:26] <mup> Bug #1754493 opened: [2.4,b1] images never finish syncing to rack controller <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1754493>
[19:08] <mup> Bug #1754493 changed: [2.4,b1] images never finish syncing to rack controller <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1754493>
[19:08] <mup> Bug #1760958 opened: [2.4] Master process changes can't notify rack controllers to start image import <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1760958>
[19:08] <mup> Bug #1760961 opened: [2.4] Domain details page: move stats to domain summary <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1760961>
[20:59] <Hey_> exit
[23:45] <dsop_> Hi all. We had a series of unfortunate events (our error) that wiped our MAAS server. We have lots of machines elisted w/ it. Question is, how can we add machines back to maas without reimaging? Or, manually mark machines from "new" to "deployed'?