=== ming is now known as Guest38993
=== ming is now known as Guest90227
h0meranyone here familiar with the cannonical openstack distro?07:26
h0merspecifically how to ssh into a glance machine deployed by JUJU?07:27
binoyhow can I power off nodes using maas . I am using WoL as power type09:11
binoy how can I power off nodes using maas GUI. I am using WoL as power type09:45
binocan anyone help me on wake on lan power type with maas12:13
bdxhows it going everyone?16:06
mupBug #1490630 opened: intermittent access issues for IPMI with HP Gen8 BL460c <MAAS:New> <https://launchpad.net/bugs/1490630>16:46
ntpttrHey everyone, I just upgraded maas from 1.7 to 1.8 by running 'sudo add-apt-repository ppa:maas-maintainers/stable' and then 'sudo apt-get dist-upgrade', and now when I go to localhost/MAAS on my browser it's stuck on a screen that says "MAAS is starting, please try again in a few seconds". Does anyone know what could make this happen?16:53
mupBug #1490637 opened: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637>16:55
roaksoaxntpttr: what does /var/log/maas/*.log say ?17:06
roaksoaxntpttr: try to access the webui again?17:06
mupBug #1490637 changed: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637>17:07
ntpttrroaksoax: It looks like reloading bind is failing, it's saying rndc connect failed:
philibarHi All, does anyone here have any information on how we can update the commission image from 14.04.1 to 14.04.3? Thank you17:12
ntpttrroaksoax: And when I try to start bind manually it fails with the same message17:12
mupBug #1490637 opened: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637>17:16
roaksoaxphilibar: you can't use point releases for commissioning images, you can however, use the latest images17:16
roaksoaxntpttr: so what does syslog say about the bind ? maybe there's a config that's making maas fail ?17:17
roaksoaxor bind fail17:17
roaksoaxphilibar: you can change the sources from 'releases' to 'daily'17:17
roaksoaxphilibar: you can change the sources from 'releases' to 'daily' images, which will give you the latest commissioning image17:17
roaksoaxphilibar: in Settings under Boot Images17:17
ntpttrroaksoax: All it's giving me is 'Reloading BIND failed: command `rndc -c /etc/bind/maas/rndc.conf.maas reload` returned non-zero exit status 1: #012rndc: connect failed: connection refused"17:19
philibarroaksoax, Thanks a bunch, we'll give that a try17:20
ntpttrroaksoax: I figured out the problem if you're interested. dnssec validation was defined both in /etc/bind/named.conf.options and /etc/bind/maas/named.conf.options.inside.maas which was causing it to fail because the configuration already existed17:41
roaksoaxntpttr: weird, MAAS should handle the upgrade gracefully17:42
roaksoaxntpttr: what version of 1.8 are you using?17:42
ntpttrroaksoax: It looks like 1.8.017:43
roaksoaxntpttr: ah yes, we fixed that in 1.8.117:47
ntpttrroaksoax: Oh, do you know how upgrading to 1.8.1 works? I didn't see too much documentation about it17:53
ntpttrroaksoax: Also, I don't know if you know much about juju as well, but I'm behind a proxy and every command I run with juju times out saying the API is unavailable17:55
roaksoaxntpttr: you can just sudo apt-get dist-upgrade to upgrade tyo 1.8.1 and 1.8.2, althoiugh, 1.8.2 will be out soon17:58
roaksoaxit is already out, it  will be available for upgrade this week17:58
roaksoaxntpttr: you probably need to set a proxy in juju too17:58
ntpttrroaksoax: I17:59
roaksoaxntpttr: https://jujucharms.com/docs/stable/howto-proxies17:59
ntpttrroaksoax: I'll check that doc out, the 'juju set-env http-proxy' command is timing out too17:59
ntpttrroaksoax: thanks for your help!18:00
roaksoaxntpttr: np! sorry cant help more with juju18:00
philibarhi roaksoax, your hack worked on getting 14.03.3, but the image does not support LTSEnablementStack, therefore the kernel does not update and doesn't fix our issue.18:18
philibarroaksoax, do you think you would know a solution on how to have a more recent kernel? I'm guessing it's by setting up a local OS repo?19:38
roaksoaxphilibar: recent kernel as in using a vivid kernel in trusty for example?19:43
philibarit's exactly that19:54
philibarwe're using HP nodes, and the driver isn't detecting the disks if we're not using vivid :(19:55
mupBug #1490709 opened: When no HWE kernels for a release, MAAS UI shows  <MAAS:New> <https://launchpad.net/bugs/1490709>20:02
roaksoaxphilibar: if you are using 1.8, change the subarchitecture for the node to amd/hwe-v *or* which is probably best, in the MAAS Settings Page20:03
roaksoaxphilibar: change the Commissioning release from trusty to Vivid20:03
roaksoaxphilibar: under the "Commissioning" section20:04
roaksoaxphilibar: i think the latter should fix your issue20:06
roaksoaxphilibar: in 1.9, however, when you *deploy* you will be able to select what kernel version you use right there instead of chnaging the subarch20:06
philibarroaksoax, we're running 1.8, and that's where I run into the issue that even if I have 15.10, 15.04, 14.10, and 14.04 LTS, we are unable to change the Commissioning release that will be used.20:07
philibarwe only have 14.04 LTS in the drop down20:07
mupBug #1490709 changed: When no HWE kernels for a release, MAAS UI shows "string index out of range" <MAAS:New for ltrager> <https://launchpad.net/bugs/1490709>20:08
roaksoaxphilibar: uhmm. Right, that means we are restricting LTS's for commissioning then20:08
roaksoaxphilibar: ok, so the other option, go to the machine details itself, and change the subarchitecture to amd64/hwe-v20:09
roaksoaxphilibar: that should do it20:09
roaksoaxphilibar: let meknow if that works20:09
philibarroaksoax, Testing now..20:10
philibarroaksoax, it works!20:16
roaksoaxphilibar: cool!20:16
philibarFinally! haha Thanks a bunch again, it has identified all my disks and went on the correct kernel20:16
roaksoaxphilibar: woohoo!20:16
mupBug #1490709 opened: When no HWE kernels for a release, MAAS UI shows  <MAAS:New> <https://launchpad.net/bugs/1490709>20:17
mupBug #1490711 opened: MAAS doesn't allow you to select what HWE kernel to use when commissioning <MAAS:Confirmed> <https://launchpad.net/bugs/1490711>20:17
philibarand right on time for me to catch my train! Thanks again20:17
philibarhave a good one roaksoax20:17
mupBug #1490711 changed: MAAS doesn't allow you to select what HWE kernel to use when commissioning <MAAS:Confirmed> <https://launchpad.net/bugs/1490711>20:23
mupBug #1490711 opened: MAAS doesn't allow you to select what HWE kernel to use when commissioning <MAAS:Confirmed> <https://launchpad.net/bugs/1490711>20:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!