no ssh access to commissioning or enlistment
Bug #1374054 reported by
Scott Moser
This bug report is a duplicate of:
Bug #1460193: MAAS needs to inject the user's SSH key into the commissioning image for debugging.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Confirmed
|
Low
|
Unassigned | ||
| maas (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
When a system boots into enlistment, it uses the appropriate ephemeral image, but there is no 'owner' of the system at that point, so no users' ssh keys are imported.
I believe the same is true for commissioning even if a user explicitly requested the commission.
The result is that if something goes wrong, no one can ssh in and see why.
It'd be good if maas had a set of ssh keys for this purpose.
| Changed in maas (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in maas: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
To post a comment you must log in.
