maas_auto_ipmi_user setting not respected
Bug #1896727 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Lee Trager | ||
Bug Description
In current master (8efb14bd37c66d
This means that if a deployment that uses that setting and recommissions machines, the ipmi user will revert back to 'maas', which might cause problems.
Related branches
~ltrager/maas:bmc_config_parameters
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 173 lines (+105/-1)3 files modifiedsrc/maasserver/forms/parameters.py (+23/-1)
src/maasserver/forms/tests/test_parameters.py (+65/-0)
src/metadataserver/builtin_scripts/commissioning_scripts/bmc_config.py (+17/-0)
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| assignee: | nobody → Lee Trager (ltrager) |
| milestone: | none → 2.9.0b4 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Marking this a Critical, since we shouldn't regress functionality like this. I'm also reluctant to upgrade our lab deployment, since we currently make use of that feature.