[enhancement] during enlistment, when maas can't create a bmc user/password, node's bmc ip address is not reported
Bug #1759911 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
| 2.4 |
Triaged
|
Medium
|
Unassigned | ||
| 2.5 |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
here's how foundation engine enlists nodes, without knowing the MAC address: http://
In cases where user/password creation on the bmc fails during enlistment, we'd like for maas to still report the BMC IP address in the power parameters, so that we can recognize the machine by its BMC IP address and set the power parameters we already have manually via the API.
example failure: https:/
| Changed in maas: | |
| milestone: | none → 2.4.0beta2 |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| assignee: | nobody → Andres Rodriguez (andreserl) |
| summary: |
- during enlistment, when maas can't create a bmc user/password, node's - bmc ip address is not reported + [enhancement] during enlistment, when maas can't create a bmc + user/password, node's bmc ip address is not reported |
| description: | updated |
| Changed in maas: | |
| milestone: | 2.4.0beta2 → 2.4.0rc1 |
| Changed in maas: | |
| milestone: | 2.4.0rc1 → 2.4.0rc2 |
| assignee: | Andres Rodriguez (andreserl) → nobody |
| Changed in maas: | |
| milestone: | 2.4.0rc2 → 2.5.0 |
| no longer affects: | maas/2.4 |
| Changed in maas: | |
| milestone: | 2.4.1 → 2.4.2 |
| Changed in maas: | |
| milestone: | 2.4.2 → 2.4.3 |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team