[09:32] <mup> Bug #1526532 opened: [xenial, 1.10] enlistment failing <python3> <MAAS:Fix Committed by blake-rouse> <maas (Ubuntu):New> <https://launchpad.net/bugs/1526532>
[11:00] <slacker27> Any update with the 1.9.2 package?
[11:31] <slacker27> I have a node that doesn't seem to get past Commissioning, using MAAS 2.0.0. The node is PXE booting and getting an IP. I have verified that the node is reachable via ping, and even attempted to ssh into it (public key denial). Are there any logs I can check on the node about it's progress?
[13:03] <mup> Bug #1562249 opened: Failed to deploy machine with HP Smart Array Raid 6i <landscape> <Landscape Server:Invalid> <MAAS:New> <https://launchpad.net/bugs/1562249>
[13:45] <mup> Bug #1526532 changed: [xenial, 1.10] enlistment failing <python3> <MAAS:Fix Committed by blake-rouse> <https://launchpad.net/bugs/1526532>
[13:45] <mup> Bug #1562249 changed: Failed to deploy machine with HP Smart Array Raid 6i <landscape> <curtin:New> <Landscape Server:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1562249>
[13:57] <mup> Bug #1562249 opened: Failed to deploy machine with HP Smart Array Raid 6i <landscape> <curtin:New> <Landscape Server:Invalid> <MAAS:Incomplete> <https://launchpad.net/bugs/1562249>
[14:18] <mup> Bug #1574113 changed: No way to inject apt archive/mirror key 'in-target' before apt starts processing packages <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1574113>
[17:03] <dimitern> mpontillo, roaksoax, blake_r: hey guy, are you aware of the issues with deploying nodes commissioned with biosdevname-enabled releases (e.g. xenial) and having too long interface names (e.g. 'enxxaabbccddeef0' for a usb2eth second NIC)?
[17:03] <dimitern> s/guy/guys/
[17:05] <dimitern> maas (and curtin) render /e/n/i in this case which cannot be applied, as creating a VLAN on such an interface (e.g. 'enxxaabbccddeef0.1234') exceeds the device name limit of 16 characters
[17:05] <dimitern> I'm filing a bug now for that
[17:22] <dimitern> https://bugs.launchpad.net/maas/+bug/1574771
[17:22] <mup> Bug #1574771 opened: MAAS/curtin generate invalid /e/n/i and failed deployment for nodes with long (biosdevname) interface names, which in turn have VLANs <networking> <robustness> <MAAS:New> <https://launchpad.net/bugs/1574771>
[17:26] <mpontillo> dimitern: thanks, good find. Hadn't seen that before; will look.
[18:19] <pronetla> Hi any can help whit my build?
[18:19] <pronetla> is very simple
[18:20] <pronetla> i can build ubuntu openstack private cloud whit 2 phisican servers?
[18:20] <pronetla> phisical*
[18:25] <mup> Bug #1574771 changed: MAAS/curtin generate invalid /e/n/i and failed deployment for nodes with long (biosdevname) interface names, which in turn have VLANs <networking> <robustness> <MAAS:Invalid> <MAAS 1.9:Invalid> <https://launchpad.net/bugs/1574771>
[19:43] <mup> Bug #1571898 changed: [2.0 beta 2] Fabric's are not created sequencially <MAAS:Invalid> <https://launchpad.net/bugs/1571898>
[21:09] <LiftedKilt> quick question - I've created a custom image in maas, and it shows up under the generated images section - but it doesn't appear in the dropdown for deployment
[21:09] <LiftedKilt> is there an additional step I need to do to ready an image for deployment?
[21:11] <roaksoax> LiftedKilt: has it been synced to the cluster controller ?
[21:11] <LiftedKilt> roaksoax: aha no - the cluster-master is saying it is out of sync
[21:11] <LiftedKilt> they are on the same machine - how do I force a sync?
[21:12] <roaksoax> LiftedKilt: is there an error of why that might be ? no issues in the logs ?
[21:14] <LiftedKilt> exceptions.IOError: Unable to open http://localhost:5240/MAAS/images-stream/custom/amd64/generic/rancheros0.4.4/20160425/root-tgz. mirrors=[]
[21:15] <roaksoax> LiftedKilt: so that's the error...now i wonder what the underlying issue might be
[21:15] <roaksoax> LiftedKilt: do you have enough disk space?
[21:16] <LiftedKilt> roaksoax: yeah I've got plenty of space
[21:16] <LiftedKilt> roaksoax: I'm going to try restarting maas-*
[21:19] <LiftedKilt> nope. didn't fix it
[21:20] <roaksoax> LiftedKilt: the weird thing is that it is an IOError, so i wonder if it is related to the image itself or something else
[21:20] <LiftedKilt> it might be - it's an image for rancherOS
[21:21] <roaksoax> LiftedKilt: never tested one of those
[21:21] <LiftedKilt> images should be in tar.gz?
[21:22] <LiftedKilt> it's available in tar.gz and iso
[21:22] <roaksoax> LiftedKilt: that's probably the reason why then
[21:22] <roaksoax> LiftedKilt: it is probably
[21:22] <roaksoax> LiftedKilt: that
[21:22] <roaksoax> LiftedKilt: the images need to be in tgz's yes
[21:23] <LiftedKilt> the image i tried uploading was a tgz
[21:23] <LiftedKilt> I was just making sure that was correct
[21:23] <roaksoax> LiftedKilt: if you could file a bug, we'll be able to look at it
[21:24] <LiftedKilt> roaksoax: ok - I'll poke at it first for a bit. I might try on 2.0 and see how that works
[21:25] <roaksoax> LiftedKilt: to be fair that codepath is fairly unchanged
[21:25] <LiftedKilt> roaksoax: ok - thanks