[07:58] <mup> Bug #1708609 opened: Virsh Pods are not detecting all storage pools <pod> <virsh> <MAAS:New> <https://launchpad.net/bugs/1708609>
[08:00] <spaok_> ello
[08:01] <spaok> anybody arounds?
[08:22] <zeih> Hi, one question regarding MAAS LDAP setup: is there a way to do it?
[09:20] <spaok> zeih: if you find a way I would love to know it
[09:20] <zeih> spaok: sure :)
[09:21] <zeih> I do not find any hint in documentation or configuration files.. so maybe it is a missing feature?
[09:22] <spaok> ya, we probably asked canonical about it a bunch times, it's a highly desired feature for me
[09:23]  * D4RKS1D3 morning
[12:31] <mup> Bug #1696752 changed: [SRU] MAAS 2.2.0 <verification-done> <verification-done-xenial> <verification-done-yakkety> <verification-done-zesty> <maas (Ubuntu):Fix
[12:31] <mup> Released> <maas (Ubuntu Xenial):Fix Released> <maas (Ubuntu Yakkety):Fix Released> <maas (Ubuntu Zesty):Fix Released> <https://launchpad.net/bugs/1696752>
[12:31] <mup> Bug #1708651 opened: [SRU] MAAS 2.2.2 <maas (Ubuntu):New> <maas (Ubuntu Xenial):New> <maas (Ubuntu Zesty):New> <https://launchpad.net/bugs/1708651>
[15:17] <mup> Bug #1708651 changed: [SRU] MAAS 2.2.2 <maas (Ubuntu):Won't Fix> <maas (Ubuntu Xenial):New> <maas (Ubuntu Zesty):New> <https://launchpad.net/bugs/1708651>
[15:17] <mup> Bug #1708679 opened: No way to read region controller image import progress through the API <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1708679>
[15:44] <mup> Bug #1708679 changed: [2.3, API] Region Controller import progress not available via API <api> <cdo-qa> <MAAS:Invalid> <https://launchpad.net/bugs/1708679>
[15:53] <mup> Bug #1708679 opened: [2.3, API] Region Controller import progress not available via API <api> <cdo-qa> <MAAS:Triaged> <https://launchpad.net/bugs/1708679>
[16:02] <mup> Bug #1708679 changed: [2.3, API] Region Controller import progress not available via API <api> <cdo-qa> <MAAS:Invalid> <https://launchpad.net/bugs/1708679>
[16:14] <bryan_att> hi - q for anyone: I'm trying to import an image (current xenial cloud image) to maas and able to import it as a "generated image" but the rack controller never completes sync, and there is no error I can see in the logs. What might be the issue?
[16:14] <mup> Bug #1708679 opened: [2.3, API] Region Controller import progress not available via API <api> <cdo-qa> <MAAS:Triaged> <https://launchpad.net/bugs/1708679>
[16:25] <roaksoax> bryan_att: what version of MAAS are you using? and hwo did you upload the image. I think the issue is the way how the image was imported. I think that may be fixed in the latest 2.2
[16:27] <bryan_att> roaksoax: v2.2.0. I uploaded it using the command "maas zbook boot-resources create name=xenial/cloud title="zzz" architecture=amd64/generic content@=/home/bryan/Downloads/xenial-server-cloudimg-amd64-disk1.img"
[16:28] <bryan_att> followed by maas zbook boot-resources import
[16:28] <bryan_att> i could not find a way to upload it using the UI
[16:29] <bryan_att> roaksoax: is there a maas issue I should follow
[17:10] <bryan_att> I also tried to import with "maas opnfv boot-resources create name=xenial/cloud title="Current xenial cloudimage" architecture=amd64/generic filetype=tgz content@=/home/bryan/xenial-server-cloudimg-amd64.tar.gz" with the same result
[17:57] <julen> Does someone have a trick to access nodes that fail commissioing when the ssh is not working?
[17:57] <julen> The keys are there, and they work for the rest of machines, but for some reason one of them opens the 22 but won't let me in
[17:58] <roaksoax> bryan_att: that's probably why
[17:58] <roaksoax> bryan_att: try uploading name=custom/cloud or  name=cloud
[17:59] <roaksoax> bryan_att: or, try name=ubuntu/cloud
[17:59] <roaksoax> although I can't remember if the fixes for the later have been backported to 2.2
[17:59] <roaksoax> ltrager: ^^
[18:00] <julen> roaksoax: do you know why was the WOL option removed?
[18:04] <roaksoax> julen: yes, we could no longer effectively supported, it was buggy and didn't work as great as we wanted to.
[18:05] <bryan_att> roaksoax:  really, the name matters? this should be just a string, or is "xenial" a reserved word? I'll try it though.
[18:11] <roaksoax> bryan_att: right so the name is "os/series" so it would be "ubuntu/custom1" or "centos/custom1" or "custom/custom1" or "windows/custom1"
[18:15] <bryan_att> roaksoax:  ok, well that seems to have worked... thanks for the help! i used "ubuntu/custom"
[18:15] <roaksoax> bryan_att: :)
[18:16] <julen> roaksoax: and do you happen to have any tip to check inside a machine where the ssh keys don't seem to work?
[18:18] <roaksoax> julen: check /var/log/maas/rsyslog/<machine-name>/<date>/messages
[18:18] <bryan_att> roaksoax: next q - now that the "generated image" is sync'd, how do I use in it deploy? It does not show up as an option in the MAAS UI for deploy.
[18:19] <roaksoax> bryan_att: 1 sec,otp
[18:19] <roaksoax> ltrager: ^^
[18:21] <ltrager> roaksoax: taking a look
[18:21] <ltrager> bryan_att: So if I understand correctly you created a custom Ubuntu image and want to deploy it?
[18:22] <bryan_att> yes, from an ubuntu cloud image
[18:22] <julen> roaksoax: but, this machine does not appear in that folder. There are only the successfully commissioned ones, and the "maas-enlisting-node" which is not the one giving the error
[18:22] <ltrager> bryan_att: do you have a link to the image you're using?
[18:23] <bryan_att> ltrager: https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64.tar.gz
[18:28] <bryan_att> ltrager: the issue I am trying to solve, other than general interest in how to manage/deploy custom images via MAAS, is that I see behavior differences between the default Ubuntu images selectable by MAAS, and other Ubuntu images (official) for the same version. These differences are resulting inconsistent ability to deploy the OpenStack-Helm project (#openstack-helm if you want to review the issues in detail). I'm not
[18:28] <bryan_att> sure what the source of the issues are, but I am trying to narrow down the variables.
[18:29] <roaksoax> ltrager: the issue here is that he uploaded name=ubuntu/custom and it is not available for deployment
[18:29] <roaksoax> ltrager: i think we already fixed that, but we dont know which
[18:31] <ltrager> roaksoax: thats in 2.2.2
[18:31] <roaksoax> ltrager: so 2.2.2 will fix that for *ubuntu* too ?
[18:31] <roaksoax> bryan_att: ^^
[18:31] <ltrager> roaksoax: I'm testing 2.2.2 for Ubuntu but I don't think that image is deployable
[18:32] <ltrager> roaksoax: I'm checking now but if I recall correctly that image doesn't include a kernel
[18:34] <ltrager> bryan_att: The images we produce come from cloud-images.ubuntu.com. We use the SquashFS image and don't modify it at all
[18:37] <bryan_att> I may be mistaken about what's possible to deploy via MAAS, just trying to see what other options I have vs the default selections. So should the other ubuntu cloud images on the same page for xenial (e.g. the one I linked above) be usable? Also re MAAS 2.2.2, is that available as a package yet, or do I have to install from source (rather not do that... it always seems to cause me to have to reimage my server if I want
[18:37] <bryan_att> to uninstall later...)
[18:38] <bryan_att> page i.e. https://cloud-images.ubuntu.com/xenial/current/ and xenial-server-cloudimg-amd64.tar.gz being the one I am trying to use
[18:39] <ltrager> bryan_att: okay nevermind that image should be deployable its another image format that doesn't contain the kernel
[18:39] <bryan_att> good - so how do I get MAAS 2.2.2 ? by source only?
[18:39] <roaksoax> bryan_att: try ppa:maas/proposed -> that holds 2.2.2 which should have the fix for havin the image deployable
[18:40] <roaksoax> bryan_att: it is being SRU'd into Xenial as we speak
[18:40] <bryan_att> roaksoax: thanks, I will do that and let you now how it goes. appreciate the help!
[18:43] <bryan_att> roaksoax: one more q - I added the ppa. how do I reference the specific version in apt-get? (as "maas" it did not upgrade it)
[18:44] <bryan_att> wait ... i did not update yet
[18:45] <roaksoax> bryan_att: sudo apt-get update :)
[18:49] <julen> roaksoax: isn't there a way to hardcode a root password during commissioning? I tried with commissioning scripts and with the curtin, but it doesn't seem to work
[18:50] <roaksoax> julen: yes, you can do it with a comissioning script, provided that the commisioning script runs
[18:50] <roaksoax> julen: are you usre it is actually pxe booting and getting metadata
[18:50] <roaksoax> julen: maybe the node is failing to run metadata
[18:51] <julen> roaksoax: hmm... I am actually not sure of the metadata
[18:52] <julen> the pxe does work, and I see that "no datasource found! Likeliy bad things to come! message, but I cannot get in to check the logs
[18:53] <roaksoax> julen: so that's the problem, eithre the machine cannot communicate with MAAS
[19:05] <julen> roaksoax: you were right. The gateway was wrong on that subnet. Thanks :)
[19:06] <roaksoax> :)
[19:40] <jamesbenson> hi, has anyone tried to deploy coreOS with MaaS?
[19:43] <roaksoax> jamesbenson: not that i know off. we can deploy Ubuntu Core though
[19:46] <jamesbenson> I haven't read up a lot about ubuntu core, how does that compare?
[19:47] <bryan_att> roaksoax: been waiting for a while after upgrading to 2.2.2 - and the image was not showing up as a deploy option in the UI - so I removed and re-added it, and it sync'd again, but still is not there as a deploy option. How do I get this image to be deployable via the UI?
[20:03] <roaksoax> ltrager: ^^
[20:03] <roaksoax> bryan_att: try adding it as name=custon/image
[20:03] <roaksoax> bryan_att: try adding it as name=custon/customimage1
[20:03] <roaksoax> bryan_att: we'll fix the issue for ubuntu/custom
[20:04] <bryan_att> "custon/customimage1" or do you mean "custom/customimage1" ?
[20:04] <roaksoax> bryan_att: name=custom/<your-image-name>" or name="<your-image-name>"
[20:05] <bryan_att> roaksoax: ok, thanks I'll try that
[20:16] <bryan_att> roaksoax: super, now it shows up as a deployable image. thanks much!
[22:30] <wililupy> Has anyone seen a node fail to deploy based on ntp failing?
[23:54] <roaksoax> wililupy: yes
[23:54] <roaksoax> wililupy: what's your failure ?