MAAS commission failed due to no IP address after shutdown

[Dave.Chen at Dell.com]

(Resend to avoid size limitation.)

Hi Developers,

I am not sure whether this email can reach you well, just cannot find a mailing list for user,

Here is my issue, I have MAAS installed on the controller, and want to commission some  nodes (Dell 9630), looks like everything is okay, MAAS release IP to nodes, nodes run some cloud init script and then shutdown, but after for an while,  MAAS claim back the IP (since I cannot find the IP anymore after clicking the DNS), and hence, MAAS cannot finish the commission, cannot get the information on Cores, RAM, disk etc.

"ping" the IP address shows me the connection cannot be established as well.

I can also see the below messages from the MAAS GUI,
"Failed to query node's BMC - Connection timed out while performing power action. Check BMC configuration and connectivity and try again."

My question is why MAAS claim back the IP from the node? Is there any configuration needed to make it works?

Attach the logs from the commission, it's

$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                            Version                      Architecture Description
+++-===============================-============================-============-=================================================
ii  maas                            2.3.5-6511-gf466fdb-0ubuntu1 all          "Metal as a Service" is a physical cloud and IPAM
ii  maas-cli                        2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS client and command-line interface
un  maas-cluster-controller         <none>                       <none>       (no description available)
ii  maas-common                     2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS server common files
ii  maas-dhcp                       2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS DHCP server
ii  maas-dns                        2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS DNS server
ii  maas-proxy                      2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS Caching Proxy
ii  maas-rack-controller            2.3.5-6511-gf466fdb-0ubuntu1 all          Rack Controller for MAAS
ii  maas-region-api                 2.3.5-6511-gf466fdb-0ubuntu1 all          Region controller API service for MAAS
ii  maas-region-controller          2.3.5-6511-gf466fdb-0ubuntu1 all          Region Controller for MAAS
un  maas-region-controller-min      <none>                       <none>       (no description available)
un  python-django-maas              <none>                       <none>       (no description available)
un  python-maas-client              <none>                       <none>       (no description available)
un  python-maas-provisioningserver  <none>                       <none>       (no description available)
ii  python3-django-maas             2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS server Django web framework (Python 3)
ii  python3-maas-client             2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS python API client (Python 3)
ii  python3-maas-provisioningserver 2.3.5-6511-gf466fdb-0ubuntu1 all          MAAS server provisioning libraries (Python 3)


Logs from "maas-enlisting-node" directory is pasted here (http://paste.openstack.org/show/734898/), highly appreciated for your help!

Best Regards,
Dave Chen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20181116/c1556b58/attachment.html>