IPMI access lost (not just maas user) after commissioning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Christian Grabowski |
Bug Description
MAAS 1:3.0.0-
I manually enlisted a system (an Ampere Mt. Jade), filling in my existing IPMI credentials for the factory default ADMIN user. Once I did so, the system began to commission as expected. However, after running 30-maas-
"Failed to query node's BMC - Access denied while performing power action: cipher suite unavailable. Check BMC configuration and try again."
So far this sounds like bug 1940319, albeit on a different model system (that was an Nvidia DGX-2). However, unlike bug 1940319, choosing a different cipher suite option in the MAAS pull down does not fix it. And worse, this doesn't just impact the newly created "maas" user. The factory default ADMIN user is also impacted, causing me to be unable to manage power or get serial-over-lan access to the console. I didn't see anything in the BMC Web UI that I could configure to correct the situation - everything looks the same on an identically configured system w/o this problem. And of course, I can't send IPMI commands to try and change cipher config because I can't authenticate. I had to resort to resetting the BMC to factory defaults.
Related branches
- MAAS Lander: Approve
- Alberto Donato (community): Approve
-
Diff: 523 lines (+70/-315)7 files modifiedsrc/maasserver/forms/parameters.py (+1/-0)
src/maasserver/forms/settings.py (+24/-1)
src/maasserver/models/config.py (+1/-0)
src/maasserver/models/tests/test_config.py (+4/-0)
src/metadataserver/builtin_scripts/commissioning_scripts/bmc_config.py (+8/-131)
src/metadataserver/builtin_scripts/commissioning_scripts/tests/test_bmc_config.py (+30/-183)
src/provisioningserver/drivers/power/ipmi.py (+2/-0)
tags: | added: blocks-hwcert-server |
Changed in maas: | |
status: | Incomplete → Fix Committed |
assignee: | nobody → Christian Grabowski (cgrabowski) |
milestone: | none → next |
Changed in maas: | |
milestone: | next → 3.2.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Could you try to commission the machine with "Allow SSH access and prevent machine powering off" checked?
Then you can ssh to the machine and check what MAAS did to the BMC.