<div>Hi Julian,</div><div><br></div><div>After a bit of investigation I think I found the problem. The problem is that when the maas-ipmi-autodetect script tries to obtain the IPMI IP Address from the BMC, 0.0.0.0 is being returned. However, the IP Address in the BMC is set correctly. So the real issue is not in the detection script, but rather it seems to be related to how the BMC cards might be exporting the data to the modules, as the same values were obtained with IPMI tool.</div> <div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>root@maas-enlisting-node:/# bmc-config --checkout | grep IP_Address</div></blockquote> <blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div># will choose to set "Static" for the "IP_Address_Source" and set the</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div># appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the machine.</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div> IP_Address_Source Use_DHCP</div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div> IP_Address 0.0.0.0</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div> Default_Gateway_IP_Address 0.0.0.0</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div> Backup_Gateway_IP_Address 0.0.0.0</div></blockquote> <blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><br></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>root@maas-enlisting-node:/# ipmitool lan print | grep IP</div></blockquote> <blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>IP Address Source : DHCP Address</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>IP Address : 0.0.0.0</div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div>Default Gateway IP : 0.0.0.0</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>Backup Gateway IP : 0.0.0.0</div></blockquote></blockquote><div><br></div><div>So what I did was to try to change the network source to Static, and then back to DHCP. Once I changed to static, the IP address was shown correctly. Then I changed it back to DHCP and the IP address was shown correctly as well. I then try to enlist/commission all over again, and this time the IP address was obtained correctly, hence the power parameters were configured correctly. This, however, only happened in one of the machines, as I wasn't able to reproduce this in the other 2 I was testing with. See below:</div> <div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>ubuntu@maas-enlisting-node:~$ sudo bmc-config --commit --key-pair="Lan_Conf:IP_Address_Source=Static"</div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>ubuntu@maas-enlisting-node:~$ sudo bmc-config --checkout | grep IP_Address</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div># will choose to set "Static" for the "IP_Address_Source" and set the </div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div># appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the machine. </div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>IP_Address_Source Static</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div><span class="Apple-tab-span" style="white-space:pre"> </span>IP_Address 192.168.2.111</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>Default_Gateway_IP_Address 192.168.2.111</div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>Backup_Gateway_IP_Address 0.0.0.0</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div><br></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>ubuntu@maas-enlisting-node:~$ sudo bmc-config --commit --key-pair="Lan_Conf:IP_Address_Source=Use_DHCP"</div></blockquote> <blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>ubuntu@maas-enlisting-node:~$ sudo bmc-config --checkout | grep IP_Address</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div># will choose to set "Static" for the "IP_Address_Source" and set the </div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div># appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the machine. </div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>IP_Address_Source Use_DHCP</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"> <div><span class="Apple-tab-span" style="white-space:pre"> </span>IP_Address 192.168.2.111</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>Default_Gateway_IP_Address 192.168.2.111</div> </blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span class="Apple-tab-span" style="white-space:pre"> </span>Backup_Gateway_IP_Address 0.0.0.0</div></blockquote></blockquote> <div><br></div><div>So I have proposed a fix [1], [2], in which it will "reset" (as above) the network source if the IP address is 0.0.0.0. This is probably the same issue as Narinder was having.</div><div><br></div> <div>Cheers.</div><div><br></div><div>[1]: <a href="https://code.launchpad.net/~andreserl/maas/1.2_reset_ipmi_network_source/+merge/137279">https://code.launchpad.net/~andreserl/maas/1.2_reset_ipmi_network_source/+merge/137279</a></div> <div>[2]: <a href="https://code.launchpad.net/~andreserl/maas/reset_ipmi_network_source/+merge/137278">https://code.launchpad.net/~andreserl/maas/reset_ipmi_network_source/+merge/137278</a></div><br><div class="gmail_quote"> On Fri, Nov 30, 2012 at 5:53 AM, Julian Edwards <span dir="ltr"><<a href="mailto:julian.edwards@canonical.com" target="_blank">julian.edwards@canonical.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Today I have tested an upgrade from the existing precise maas package to<br> the version in the daily builds PPA (build from the 1.2 branch and the<br> packaging.precise.sru packaging branch):<br> <br> 0.1+bzr1309+dfsg-0+1314+148~ppa0~precise1<br> <br> I have enabled -proposed and I am also using the python-txtftp package<br> in the daily builds PPA since that is not backported to precise yet, and<br> also raphael - 2.1.0-0ubuntu4~12.04.2~ppa1 which is not backported to<br> precise.<br> <br> NB. I am not testing the remote cluster scenario, region and cluster are<br> on the same machine.<br> <br> <br> Package Upgrade and UI<br> ======================<br> <br> Just a few small things to note:<br> <br> 1. pserv.yaml comes up as a conflicting config, but it *must* be updated<br> or the pserv will never start up.<br> <br> 2. maas_local_settings.py comes up as a conflicting config, also must be<br> updated<br> <br> However everything else seems to work! Both the cluster and the<br> region's celery are running. the pserv is running, and I can access the<br> UI.<br> <br> Node enlistment, commissioning and deployment<br> =============================================<br> <br> After upgrade, you need to install the maas-dhcp and maas-dns packages,<br> and then head to the UI to configure the cluster controller.<br> <br> * Enlistment worked fine using precise, but with quantal it hangs when<br> detecting the BMC (this is on my HP microservers, with or without the<br> extra kernel params enabled). The BMC parameters were not detected.<br> * Commissioning fine (with precise) - but this time BMC parameters<br> detected ok!<br> * juju bootstrap - worked ok, commissioned machine powers up<br> * juju deploy mysql - worked ok<br> * juju deploy wordpress - worked ok<br> * juju add-relation and then expose, all ok<br> <br> So in summary, there's two problems:<br> 1. BMC detection. Seems to half work.<br> 2. enlisting with quantal hangs.<br> <br> Cheers.<br> <span><font color="#888888"><br> --<br> Mailing list: <a href="https://launchpad.net/~maas-devel" target="_blank">https://launchpad.net/~maas-devel</a><br> Post to : <a href="mailto:maas-devel@lists.launchpad.net" target="_blank">maas-devel@lists.launchpad.net</a><br> Unsubscribe : <a href="https://launchpad.net/~maas-devel" target="_blank">https://launchpad.net/~maas-devel</a><br> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br> </font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Andres Rodriguez (RoAkSoAx)<br>Ubuntu Server Developer<br>Systems Engineer<br>