=== edamato is now known as edamato-afk === edamato-afk is now known as edamato [15:02] roaksoax: Hi Andres… I need to test quite a few things before I can fix bug 1130232. Do you have the precise django package that we intend to SRU (i.e. the one *without* the genericipaddressfield.diff patch)? If you don't have it handy, could you please create it… that would help me a great deal. [15:02] bug 1130232 in MAAS "Implement GenericIpAddressField in MAAS rather than django." [Undecided,New] https://launchpad.net/bugs/1130232 [15:06] rvba: howdy!! sure give me a sec [15:09] rvba: and re on the comments, yeah I was looking this as a patch because this should only apply to precise, and not quantal :) [15:09] but i guess that's clear now [15:10] roaksoax: it is clear. I'm still a bit unsure what's the best solution… but what's sure is that we will have to carry this damn field one way or another. I mean in MAAS' code and not as a patch on Django. [15:10] rvba: yeah!! it is a blocker for sure! but something needed to be done to satisfy the tech board. [15:12] rvba: ok just uploaded to ppa:maas-maintainers/experimental [15:12] roaksoax: thanks a lot [15:12] should take a while till it gets accepted, built and released (~20mins) [15:18] hey http://jujucharms.com/charms/precise/nova-cloud-controller/config does not mention vlanmanager mode for the network [15:19] does it mean it s not possible to use vlanmanager mode with a maas installed openstack ? === matsubara is now known as matsubara-lunch === matsubara-lunch is now known as matsubara [18:23] roaksoax: we are hitting https://bugs.launchpad.net/maas/+bug/1116700 [18:24] Launchpad bug 1116700 in MAAS 1.2 "CNAME not added if PXE iface is different from first one in DB" [Critical,Fix committed] [18:24] btw I hope you feel better :) [18:25] any clue what's best if we wanted to stick to maas-developers/stable [19:17] racedo: i could make a new release [19:17] so you guys using an interface which is different from eth0? [19:17] for the PXE booting and it is not generating the CNAME's"? [19:26] roaksoax: yes, thats the problem [19:26] racedo: are you hitting this with a costumer? [19:26] we see a name in the maas web ui but it never gets added to the bind zone file [19:27] roaksoax: yes [19:27] we are onsite [19:27] racedo: s/costumer/customer [19:27] racedo: ok, so I think I can prepare a package with the fix included, but it will take me a few to test it [19:27] so all the nodes that pxe boot from eth0 get added to the dns file after enlisting [19:28] and the node (just 1) that boots from eth1 is not added but we get a name created and shown in the web ui [19:29] roaksoax: ok, thanks for that [19:29] we'll be here (NJ) for the day [19:29] racedo: only today? [19:30] roaksoax: today until 6 and tomorrow all day again [19:30] racedo: ok cool, so that gives me some time :) [19:30] sure man, no rush :) [19:30] racedo: what else would you need? What iLO version are they using? [19:30] 1.33 [19:30] racedo: ok so old implementation works well then [19:31] but we are hitting some issues with version 1.29 they fail though [19:31] roaksoax: we have ipmi 1.33 working fine and 3 hosts with ipmi 1.29 failing but they will try to upgrade them [19:32] btw we are using ppa:maas-maintainers/stable [19:32] racedo: ok, can you manually access IPMI with the maas credentials? [19:33] roaksoax: no, they ping and that's all we get [19:34] we think it's on the nodes' ipmi side [19:34] racedo: right, but can you access with admin credentials? [19:36] roaksoax: no, it's stuck, nothing happens, we think it's faulty i'm going to double check [19:37] racedo: ok! [20:00] roaksoax: ok they just upgraded the ipmi to 2.66 and this is what happens https://pastebin.canonical.com/85181/ [20:00] BMC error [20:00] racedo: what about if you use the admin credentials? [20:05] roaksoax: just got the credentials [20:05] it works [20:05] roaksoax: https://pastebin.canonical.com/85182/ [20:06] racedo: alright, so something is busted in the IPMI creation stuff [20:06] racedo: the new precise update should be able to fix that [20:06] (i hope [20:06] ra unless you provide me with output of what happened during the enlistment process [20:06] you mean freeipmi-tools pkg? [20:06] to see if it was able to successfully detect IPMI [20:07] racedo: yeah that might be it, it might have failed [20:07] to install [20:07] racedo: are you guys using a proxy? [20:07] no [20:07] oh squid-deb-proxy [20:08] racedo: right, so you probably need to allow the enlistment/commissioning images to access a proxy [20:08] we got the last version apparently: https://pastebin.canonical.com/85183/ [20:08] roaksoax: ok, what would that do? [20:08] racedo: yeah but the commissioning images also need proxy access [20:08] racedo: give me a sec! [20:08] sure man [20:11] racedo: do this: https://pastebin.canonical.com/85185/ and pastebinit for me please [20:12] https://pastebin.canonical.com/85186/ [20:13] racedo: ok so it seems that the user gets added correctly, but what is not done correctly is to provide a privilege for it === matsubara is now known as matsubara-afk [20:16] roaksoax: ok [20:16] and can we set the ipmi to allow it? [20:16] racedo: can ytou do something like this? https://pastebin.canonical.com/85187/ [20:19] and then try to stat the node [20:19] trying hold on a sec [20:21] racedo: ok, so I have a package that I just uploaded to ppa:maas-maintainers/testing that I will test, and then release in ppa:maas-maintainers/stable [20:24] roaksoax: we are reenlisting it now [20:24] racedo: cool [20:25] roaksoax: thanks for the package too! [20:27] roaksoax: you fixed it! [20:28] racedo: cool!! I wonder why it didn't work out of the box as it should have! [20:28] probably due to the older ipmi version [20:28] oh that could be the case [20:56] racedo: ok, the package should be published really soon [20:56] ~10 mins or so [20:56] if not less [21:04] racedo: its done! you should be able to upgrade now [21:18] roaksoax: thats awesome!! [21:18] trying it now [21:27] roaksoax: fixed [21:27] roaksoax: many thanks again :) [21:27] roaksoax++ [21:30] racedo: no probs. just confirm it upgrades and works fine :) [21:30] it has upgraded fine [21:30] and now the host can boot out of eth1 [21:30] confirmed [21:32] cool === kentb is now known as kentb-out