[2.5] BMC Enlistment - When the machine commissionins/runs hardware testing, there are no cloud-init event stored
Bug #1782007 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
When we add a machine via BMC enlistment, or when the machines commission on enlistment, there are no event messages that come from cloud-init stored.
| Changed in maas: | |
| milestone: | none → 2.5.0 |
| importance: | Undecided → Medium |
| tags: | added: bmc-enlistment |
| Changed in maas: | |
| status: | New → Triaged |
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| milestone: | 2.5.0 → 2.5.0alpha2 |
| Changed in maas: | |
| milestone: | 2.5.0alpha2 → 2.5.0beta1 |
| Changed in maas: | |
| milestone: | 2.5.0beta1 → 2.5.0beta2 |
| Changed in maas: | |
| milestone: | 2.5.0beta2 → 2.5.0rc1 |
| Changed in maas: | |
| milestone: | 2.5.0rc1 → 2.5.x |
Revision history for this message
| Adam Collard (adam-collard) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
When a new machine is BMC enlisted the machine boots without OAUTH credentials. Everything cloud-init interacts with is over the anonymous API handlers. The anonymous handler doesn't log cloud-init messages because it doesn't know what machine the messages are related to.
BMC enlistment happens when the maas-enlist script sends the BMC credentials so MAAS can look them up and return a node object. By the time it does this its already lost many messages. Even after we have the OAUTH credentials there is no way to tell cloud-init to use a new endpoint for messages.