[05:48] <mup> Bug #1662073 opened: 'regiond' tries to get 'bootloaders' that are not selected <MAAS:New> <https://launchpad.net/bugs/1662073>
[09:45] <mup> Bug #1662111 opened: when deploying 'virsh' type of machine(KVM), it repeats deploying constantly <MAAS:New> <https://launchpad.net/bugs/1662111>
[13:28] <mup> Bug #1661880 changed: specify static ip address when taking ownership of device <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1661880>
[14:37] <mup> Bug #1662185 opened: device discovery runs correctly, at first, but not subsequently <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1662185>
[17:58] <mup> Bug #1662274 opened: When maas gui tells you to install some packages, it should offer to do so for you <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1662274>
[18:07] <mup> Bug #1662274 changed: When maas gui tells you to install some packages, it should offer to do so for you <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1662274>
[18:16] <mup> Bug #1662274 opened: When maas gui tells you to install some packages, it should offer to do so for you <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1662274>
[18:30] <mmxe> Hi
[18:30] <mmxe> Does anyone have any idea what's going on with the error in the log I posted over the weekend?
[18:31] <mmxe> The error occurs during commissioning process. My commisioning fails and the only error I see is that ssh keys weren't installed for user ubuntu
[18:31] <mmxe> I've added ssh keys to my MAAS user account.
[18:47] <pmatulis> mmxe, best file a bug. include all logs. not just a snippet
[19:13] <roaksoax> mmxe: it seems the amchine is trying to enlist, not commission
[19:14] <roaksoax> mmxe: the issue doens't seem to be the ssh keys
[19:14] <roaksoax> mmxe: but cloud-init dying for some reason
[19:14] <roaksoax> mmxe: what version of MAAS are you using ?
[19:17] <pmatulis> he said 2.1.3 earlier
[19:29] <roaksoax> ah!
[19:29] <roaksoax> mmxe: make sure you have the latest images as well
[19:52] <mmxe> I have the images that MAAS downloaded automatically.
[19:53] <mmxe> On a side note, it would be nice to see the MAC addresses associated with DHCP leases in the lease list so it's easier to fill out power control MACs and IP.
[19:53] <mmxe> It's sort of a convoluted process to pair a MAC with a machine name.
[19:54] <roaksoax> mmxe: you dont need MAC's for BMC's
[19:55] <mmxe> I select IPMI as my "Power type" and the last field is "Power MAC"
[19:55] <mmxe> It's not necessary to populate it?
[21:00] <roaksoax> mmxe: no it is not
[21:02] <mup> Bug #1657491 opened: Several IPs assigned to the same iface in the DB due to 'free' leases <sts> <MAAS:In Progress by mpontillo> <https://launchpad.net/bugs/1657491>
[22:02] <mup> Bug #1662343 opened: [2.1.3] Commissioning doesn't pick up new storage devices <oil> <MAAS:New> <https://launchpad.net/bugs/1662343>
[22:05] <mup> Bug #1662343 changed: [2.1.3] Commissioning doesn't pick up new storage devices <oil> <MAAS:New> <https://launchpad.net/bugs/1662343>
[22:20] <mup> Bug #1662343 opened: [2.1.3] Commissioning doesn't pick up new storage devices <oil> <MAAS:New> <https://launchpad.net/bugs/1662343>
[23:25] <catbus1> roaksoax: Hi, I tried to add maas cloud to conjure-up, but it errors out with trackback: unable to find: <home folder>/.local/share/juju/accounts.yaml. Is there something I need to do prior to setting this up in conjure-up?
[23:33] <catbus1> or 'cattle' not found in juju's bootstrap-config.yaml
[23:38] <mup> Bug #1662361 opened: `machine deploy` parameter expectations and error output are not consistent <uosci> <MAAS:New> <https://launchpad.net/bugs/1662361>