| === ming is now known as Guest38993 | ||
| === ming is now known as Guest90227 | ||
| h0mer | anyone here familiar with the cannonical openstack distro? | 07:26 |
|---|---|---|
| h0mer | specifically how to ssh into a glance machine deployed by JUJU? | 07:27 |
| binoy | Hi | 09:10 |
| binoy | how can I power off nodes using maas . I am using WoL as power type | 09:11 |
| binoy | how can I power off nodes using maas GUI. I am using WoL as power type | 09:45 |
| bino | hi | 11:46 |
| bino | can anyone help me on wake on lan power type with maas | 12:13 |
| bdx | hows it going everyone? | 16:06 |
| bdx | http://askubuntu.com/questions/666572/how-to-add-user-defined-cloud-config-preseed-in-maas | 16:07 |
| mup | Bug #1490630 opened: intermittent access issues for IPMI with HP Gen8 BL460c <MAAS:New> <https://launchpad.net/bugs/1490630> | 16:46 |
| ntpttr | Hey 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 |
| mup | Bug #1490637 opened: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637> | 16:55 |
| roaksoax | ntpttr: what does /var/log/maas/*.log say ? | 17:06 |
| roaksoax | ntpttr: try to access the webui again? | 17:06 |
| mup | Bug #1490637 changed: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637> | 17:07 |
| ntpttr | roaksoax: It looks like reloading bind is failing, it's saying rndc connect failed: 127.0.0.1#954 | 17:10 |
| philibar | Hi All, does anyone here have any information on how we can update the commission image from 14.04.1 to 14.04.3? Thank you | 17:12 |
| ntpttr | roaksoax: And when I try to start bind manually it fails with the same message | 17:12 |
| mup | Bug #1490637 opened: Devices model should support types (container) <MAAS:New> <https://launchpad.net/bugs/1490637> | 17:16 |
| roaksoax | philibar: you can't use point releases for commissioning images, you can however, use the latest images | 17:16 |
| roaksoax | ntpttr: so what does syslog say about the bind ? maybe there's a config that's making maas fail ? | 17:17 |
| roaksoax | or bind fail | 17:17 |
| roaksoax | philibar: you can change the sources from 'releases' to 'daily' | 17:17 |
| roaksoax | philibar: you can change the sources from 'releases' to 'daily' images, which will give you the latest commissioning image | 17:17 |
| roaksoax | philibar: in Settings under Boot Images | 17:17 |
| ntpttr | roaksoax: 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: 127.0.0.1#954: connection refused" | 17:19 |
| philibar | roaksoax, Thanks a bunch, we'll give that a try | 17:20 |
| ntpttr | roaksoax: 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 existed | 17:41 |
| roaksoax | ntpttr: weird, MAAS should handle the upgrade gracefully | 17:42 |
| roaksoax | ntpttr: what version of 1.8 are you using? | 17:42 |
| ntpttr | roaksoax: It looks like 1.8.0 | 17:43 |
| roaksoax | ntpttr: ah yes, we fixed that in 1.8.1 | 17:47 |
| ntpttr | roaksoax: Oh, do you know how upgrading to 1.8.1 works? I didn't see too much documentation about it | 17:53 |
| ntpttr | roaksoax: 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 unavailable | 17:55 |
| roaksoax | ntpttr: 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 soon | 17:58 |
| roaksoax | it is already out, it will be available for upgrade this week | 17:58 |
| roaksoax | ntpttr: you probably need to set a proxy in juju too | 17:58 |
| ntpttr | roaksoax: I | 17:59 |
| roaksoax | ntpttr: https://jujucharms.com/docs/stable/howto-proxies | 17:59 |
| ntpttr | roaksoax: I'll check that doc out, the 'juju set-env http-proxy' command is timing out too | 17:59 |
| ntpttr | roaksoax: thanks for your help! | 18:00 |
| roaksoax | ntpttr: np! sorry cant help more with juju | 18:00 |
| philibar | hi 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 |
| philibar | roaksoax, 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 |
| roaksoax | philibar: recent kernel as in using a vivid kernel in trusty for example? | 19:43 |
| philibar | yes | 19:53 |
| philibar | it's exactly that | 19:54 |
| philibar | we're using HP nodes, and the driver isn't detecting the disks if we're not using vivid :( | 19:55 |
| mup | Bug #1490709 opened: When no HWE kernels for a release, MAAS UI shows <MAAS:New> <https://launchpad.net/bugs/1490709> | 20:02 |
| roaksoax | philibar: 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 Page | 20:03 |
| roaksoax | philibar: change the Commissioning release from trusty to Vivid | 20:03 |
| roaksoax | philibar: under the "Commissioning" section | 20:04 |
| roaksoax | philibar: i think the latter should fix your issue | 20:06 |
| roaksoax | philibar: in 1.9, however, when you *deploy* you will be able to select what kernel version you use right there instead of chnaging the subarch | 20:06 |
| philibar | roaksoax, 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 |
| philibar | we only have 14.04 LTS in the drop down | 20:07 |
| mup | Bug #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 |
| roaksoax | philibar: uhmm. Right, that means we are restricting LTS's for commissioning then | 20:08 |
| roaksoax | philibar: ok, so the other option, go to the machine details itself, and change the subarchitecture to amd64/hwe-v | 20:09 |
| roaksoax | philibar: that should do it | 20:09 |
| roaksoax | philibar: let meknow if that works | 20:09 |
| philibar | roaksoax, Testing now.. | 20:10 |
| philibar | YESSSS! | 20:16 |
| philibar | roaksoax, it works! | 20:16 |
| roaksoax | philibar: cool! | 20:16 |
| philibar | Finally! haha Thanks a bunch again, it has identified all my disks and went on the correct kernel | 20:16 |
| roaksoax | philibar: woohoo! | 20:16 |
| mup | Bug #1490709 opened: When no HWE kernels for a release, MAAS UI shows <MAAS:New> <https://launchpad.net/bugs/1490709> | 20:17 |
| mup | Bug #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 |
| philibar | and right on time for me to catch my train! Thanks again | 20:17 |
| philibar | have a good one roaksoax | 20:17 |
| mup | Bug #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 |
| mup | Bug #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!