=== wolverin_ is now known as wolverineav_ [04:25] Bug #1589951 changed: why pxe booted node is stucked in commissioning status === jamespag` is now known as jamespage [08:07] 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] So the juju agent on it was permanently lost. [08:08] But it's no problem with the LXC containers on that physical machine. [08:10] Is there any way to solve this problem? Thanks in advanced. [08:10] By the way, it seems no such kind of issue in MAAS 2.0 rc3. === mwhudson_ is now known as mwhudson [12:11] Bug #1611342 opened: UI error while generating a MAAS key (token) [13:49] hi! i imported a windows image, but i cannot select it for deployment. where can i find any docs or hints?? [15:03] Bug #1598301 changed: Deploying centos7 fails during cloud-init networking

=== frankban is now known as frankban|afk [17:31] 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] Bug #1611481 opened: IPMI autoconfiguration and startup not working [19:12] Bug #1611481 changed: IPMI autoconfiguration and startup not working [19:15] Bug #1611481 opened: IPMI autoconfiguration and startup not working [19:52] /win 4 === menn0 is now known as menn0-exercise [22:16] Bug #1281758 opened: re-installing maas-region-controller fails [22:16] Bug #1281758 opened: re-installing maas-region-controller fails === menn0-exercise is now known as menn0 [22:26] 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] i can't tell if this is common or if this is something simple i'm overlooking in my deployment. [23:19] i verified that the switch isn't doing anything to prevent ports from coming up or anything... [23:24] v1k0d3n: that seems like a curtin issue [23:24] v1k0d3n: what are you doing ? trying to deploy a machine? [23:24] yeah, only starting the pxe boot process for a machine. [23:25] v1k0d3n: so the machine PXE boots into the ephemeral environment, and then it fails with that message ? [23:25] during installation? [23:25] 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] pxe appears to load the image and the kernel. then i get that message. [23:25] let me start again and give you details. [23:26] is there a way to get more debug info? [23:26] v1k0d3n: interesting... so it doesn't even boot into Ubuntu ? [23:27] no. doesn't seem so. [23:27] should somehting be in the maas logs? [23:27] v1k0d3n: what version is it booting ? [23:27] v1k0d3n: if you can pastebin your logs [23:27] that'd be good [23:27] i am really new at maas, so not familiar with the boot process really. [23:27] v1k0d3n: what version of MAAS are you booting ? [23:28] 2.0.0 rc2+bzr5156 [23:28] this is what "comes" with apt 16.04 [23:28] strange, i've not seen that before [23:29] but my guess is that it may be a error with the kernel [23:29] v1k0d3n: if you can grab a console log, that'd be great [23:29] hmmm [23:29] is this logged on the maas server, i guess? [23:30] looking in var/log/maas currently [23:30] v1k0d3n: so how are you watching your server boot ? [23:30] console. things are kind of going quickly out of view. [23:30] it's an infinite loop of mdadm: CREATE group/user disk/root not found [23:31] v1k0d3n: yeah that seems like a kernel bug [23:32] so more people are experiencing this as well? [23:37] sorry for the questions...is there a recommendation? i've tried this a handful of times with no luck.