MAAS 2.0.0 cannot commission Dell PowerEdge R610

[Nicholas Loulloudes]

Hi,

I run to an issue where MAAS 2.0.0 (beta3+bzr4941) cannot commission my Dell PowerEdge R610 servers. Nodes get enlisted correctly, but commission fails. All other nodes in the same network, (IBM and HP) are commissioned and deployed without any issues.

Commissioning distros used so far are 16.04 and 14.04 LTS. Also DHCP and DNS are unmanaged.

Some additional Information below:

1. MAAS runs on Ubuntu 16.04 LTS
2. Failing machine hostname: nc3
3. MAAS log files (/var/log/maas/*.log and /var/log/maas/rsyslog/*.log) are attached
4. Commissioning Script from WebGUI not available, because machine never get's commissioned.
5. During commissioning I clicked on "Allow SSH ...." - However could not login it to get /var/log/cloud-init-*
6. Full Event Log (WebGUI) of the machine that fails as follows:

Happy to provide any additional logs / info you might need to track down this issue.

[Nicholas Loulloudes (loulloudes.n)]

WebGui Event Log

[Andres Rodriguez (andreserl)]

Hi Nicholas,

I have one last question. Is this a system with HPDSA or HPVSA array ?

[Nicholas Loulloudes (loulloudes.n)]

Hi Andres,

It's a Dell machine, so IFAIK they don't come with HPDSA/HPVSA arrays - but I might be mistaken.

It has a PERC Raid controller, with only 1 300GB SAS drive (no RAID config)

[Nicholas Loulloudes (loulloudes.n)]

Some more information I recorded today from testing

- Any "Commission" or "Deployment" action from MAAS (triggered via IPMI v2) causes the server to go into a erratical reboot loop
- After some reboot cycles (4-5) the server powers off.
- This behavior is present to 3 other R610 servers with exactly the same hardware configuration.
- Due to the reboot-loop, MAAS cannot communicate with the server - hence it reports that "Commissioning" fails

- I managed to Commission the server manually as follows:
   - While the server is physiallcy power-off, I go to the MAAS WebGUI and change its Power Mode to "Manual"
   - Then select and execute "Abort" commissioning
   - Then select and execute "Commissioning'
   - Then physically power-on the server (manually press Power button)
   - Server boots normally (no loops), contacts MAAS and gets the Ubuntu commissioning image
   - After a while, MAAS reports that the server is now Commissioned
   - The server is now accessible via SSH

[Nicholas Loulloudes (loulloudes.n)]

R610 system information

- BIOS ver: 6.4.0
- iDRAC 6 ver: 2.85 (Build 04)
- Lifecycle Controller Firmware ver: 1.7.5.4

[Brandyn Abel (techy2493)]

Not to beat a dead horse but I am attempting to comission a similar server Poweredge R620 and am noticing the same issue.