maas-devel team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxx>]

Hi Julian,

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.

root@maas-enlisting-node:/# bmc-config --checkout | grep IP_Address

# will choose to set "Static" for the "IP_Address_Source" and set the

# appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the
machine.

        IP_Address_Source                             Use_DHCP

        IP_Address                                    0.0.0.0

        Default_Gateway_IP_Address                    0.0.0.0

        Backup_Gateway_IP_Address                     0.0.0.0


root@maas-enlisting-node:/# ipmitool lan print | grep IP

IP Address Source       : DHCP Address

IP Address              : 0.0.0.0

IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10

Default Gateway IP      : 0.0.0.0

Backup Gateway IP       : 0.0.0.0


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:

ubuntu@maas-enlisting-node:~$ sudo bmc-config --commit
--key-pair="Lan_Conf:IP_Address_Source=Static"

ubuntu@maas-enlisting-node:~$ sudo bmc-config --checkout | grep IP_Address

# will choose to set "Static" for the "IP_Address_Source" and set the

# appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the
machine.

IP_Address_Source                             Static

IP_Address                                    192.168.2.111

Default_Gateway_IP_Address                    192.168.2.111

Backup_Gateway_IP_Address                     0.0.0.0


ubuntu@maas-enlisting-node:~$ sudo bmc-config --commit
--key-pair="Lan_Conf:IP_Address_Source=Use_DHCP"

ubuntu@maas-enlisting-node:~$ sudo bmc-config --checkout | grep IP_Address

# will choose to set "Static" for the "IP_Address_Source" and set the

# appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the
machine.

IP_Address_Source                             Use_DHCP

IP_Address                                    192.168.2.111

Default_Gateway_IP_Address                    192.168.2.111

Backup_Gateway_IP_Address                     0.0.0.0


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.

Cheers.

[1]:
https://code.launchpad.net/~andreserl/maas/1.2_reset_ipmi_network_source/+merge/137279
[2]:
https://code.launchpad.net/~andreserl/maas/reset_ipmi_network_source/+merge/137278

On Fri, Nov 30, 2012 at 5:53 AM, Julian Edwards <
julian.edwards@xxxxxxxxxxxxx> wrote:

> Today I have tested an upgrade from the existing precise maas package to
> the version in the daily builds PPA (build from the 1.2 branch and the
> packaging.precise.sru packaging branch):
>
> 0.1+bzr1309+dfsg-0+1314+148~ppa0~precise1
>
> I have enabled -proposed and I am also using the python-txtftp package
> in the daily builds PPA since that is not backported to precise yet, and
> also raphael - 2.1.0-0ubuntu4~12.04.2~ppa1 which is not backported to
> precise.
>
> NB. I am not testing the remote cluster scenario, region and cluster are
> on the same machine.
>
>
> Package Upgrade and UI
> ======================
>
> Just a few small things to note:
>
> 1. pserv.yaml comes up as a conflicting config, but it *must* be updated
> or the pserv will never start up.
>
> 2. maas_local_settings.py comes up as a conflicting config, also must be
> updated
>
> However everything else seems to work!  Both the cluster and the
> region's celery are running. the pserv is running, and I can access the
> UI.
>
> Node enlistment, commissioning and deployment
> =============================================
>
> After upgrade, you need to install the maas-dhcp and maas-dns packages,
> and then head to the UI to configure the cluster controller.
>
>  * Enlistment worked fine using precise, but with quantal it hangs when
> detecting the BMC (this is on my HP microservers, with or without the
> extra kernel params enabled).  The BMC parameters were not detected.
>  * Commissioning fine (with precise) - but this time BMC parameters
> detected ok!
>  * juju bootstrap - worked ok, commissioned machine powers up
>  * juju deploy mysql - worked ok
>  * juju deploy wordpress - worked ok
>  * juju add-relation and then expose, all ok
>
> So in summary, there's two problems:
> 1. BMC detection.  Seems to half work.
> 2. enlisting with quantal hangs.
>
> Cheers.
>
> --
> Mailing list: https://launchpad.net/~maas-devel
> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maas-devel
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
Systems Engineer