[04:25] <mup> Bug #1589951 changed: why pxe booted node is stucked in commissioning status <MAAS:Expired> <https://launchpad.net/bugs/1589951>
[08:07] <godleon> Hi all, I can not get the same ip address after power on an power-down suddenly physical machine in MAAS 1.9.3.
[08:08] <godleon> So the juju agent on it was permanently lost.
[08:08] <godleon> But it's no problem with the LXC containers on that physical machine.
[08:10] <godleon> Is there any way to solve this problem? Thanks in advanced.
[08:10] <godleon> By the way, it seems no such kind of issue in MAAS 2.0 rc3.
[12:11] <mup> Bug #1611342 opened: UI error while generating a MAAS key (token) <sts> <MAAS:New> <https://launchpad.net/bugs/1611342>
[13:49] <kuglgruber> hi! i imported a windows image, but i cannot select it for deployment. where can i find any docs or hints??
[15:03] <mup> Bug #1598301 changed: Deploying centos7 fails during cloud-init networking <MAAS:Invalid> <maas-images:Triaged> <https://launchpad.net/bugs/1598301>
[17:31] <Sina_Maleki> Hi friends i am on a fresh install of openstack via maas and lanscape but at adding juju there is problem can anyone help me ?
[19:06] <mup> Bug #1611481 opened: IPMI autoconfiguration and startup not working <MAAS:New> <https://launchpad.net/bugs/1611481>
[19:12] <mup> Bug #1611481 changed: IPMI autoconfiguration and startup not working <MAAS:New> <https://launchpad.net/bugs/1611481>
[19:15] <mup> Bug #1611481 opened: IPMI autoconfiguration and startup not working <MAAS:New> <https://launchpad.net/bugs/1611481>
[19:52] <roaksoax>  /win 4
[22:16] <mup> Bug #1281758 opened: re-installing maas-region-controller fails <docteam> <MAAS:New> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1281758>
[22:16] <mup> Bug #1281758 opened: re-installing maas-region-controller fails <docteam> <MAAS:New> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1281758>
[22:26] <v1k0d3n> hey all...i'm new to maas and been fighting through a condition lately that i can seem to figure out. i'm receiving a "mdadm: CREATE group/user disk/root not found". have others been experiencing this as well?
[22:26] <v1k0d3n> i can't tell if this is common or if this is something simple i'm overlooking in my deployment.
[23:19] <v1k0d3n> i verified that the switch isn't doing anything to prevent ports from coming up or anything...
[23:24] <roaksoax> v1k0d3n: that seems like a curtin issue
[23:24] <roaksoax> v1k0d3n: what are you doing ? trying to deploy a machine?
[23:24] <v1k0d3n> yeah, only starting the pxe boot process for a machine.
[23:25] <roaksoax> v1k0d3n: so the machine PXE boots into the ephemeral environment, and then it fails with that message ?
[23:25] <roaksoax> during installation?
[23:25] <v1k0d3n> been trying to research over the last couple of days...but seems like it can go in any direction. figured i'd ask here...just to see if there are any known issues.
[23:25] <v1k0d3n> pxe appears to load the image and the kernel. then i get that message.
[23:25] <v1k0d3n> let me start again and give you details.
[23:26] <v1k0d3n> is there a way to get more debug info?
[23:26] <roaksoax> v1k0d3n: interesting... so it doesn't even boot into Ubuntu ?
[23:27] <v1k0d3n> no. doesn't seem so.
[23:27] <v1k0d3n> should somehting be in the maas logs?
[23:27] <roaksoax> v1k0d3n: what version is it booting ?
[23:27] <roaksoax> v1k0d3n: if you can pastebin your logs
[23:27] <roaksoax> that'd be good
[23:27] <v1k0d3n> i am really new at maas, so not familiar with the boot process really.
[23:27] <roaksoax> v1k0d3n: what version of MAAS are you booting ?
[23:28] <v1k0d3n> 2.0.0 rc2+bzr5156
[23:28] <v1k0d3n> this is what "comes" with apt 16.04
[23:28] <roaksoax> strange, i've not seen that before
[23:29] <roaksoax> but my guess is that it may be a error with the kernel
[23:29] <roaksoax> v1k0d3n: if you can grab a console log, that'd be great
[23:29] <v1k0d3n> hmmm
[23:29] <v1k0d3n> is this logged on the maas server, i guess?
[23:30] <v1k0d3n> looking in var/log/maas currently
[23:30] <roaksoax> v1k0d3n: so how are you watching your server boot ?
[23:30] <v1k0d3n> console. things are kind of going quickly out of view.
[23:30] <v1k0d3n> it's an infinite loop of mdadm: CREATE group/user disk/root not found
[23:31] <roaksoax> v1k0d3n: yeah that seems like a kernel bug
[23:32] <v1k0d3n> so more people are experiencing this as well?
[23:37] <v1k0d3n> sorry for the questions...is there a recommendation? i've tried this a handful of times with no luck.