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
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