MAAS needs to inject the user's SSH key into the commissioning image for debugging
Bug #1460193 reported by
Andres Rodriguez
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
When commissioning a machine, and if it failed, there's no way for the user to ssh into the image. MAAS needs to inject the SSH key so the user can ssh in (this is the key of the admin user who decided to commission the machine).
Related bugs:
* bug 1462498: install environment should not let user in as 'ubuntu'
Related branches
lp:~andreserl/maas/lp1460193
- Andres Rodriguez (community): Approve
- Blake Rouse (community): Approve
-
Diff: 770 lines (+617/-2)10 files modifiedetc/maas/templates/commissioning-user-data/user_data.template (+7/-0)
src/maasserver/api/nodes.py (+19/-0)
src/maasserver/migrations/0176_add_enable_ssh_and_block_poweroff_commissioning_attributes.py (+495/-0)
src/maasserver/models/node.py (+28/-0)
src/maasserver/models/tests/test_node.py (+37/-0)
src/maasserver/tests/test_preseed.py (+1/-1)
src/maasserver/websockets/handlers/device.py (+2/-0)
src/maasserver/websockets/handlers/node.py (+2/-0)
src/metadataserver/api.py (+4/-1)
src/metadataserver/tests/test_api.py (+22/-0)
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| tags: | added: ui |
| tags: | added: ux |
| description: | updated |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
from the duplicate bug 1374054, access into enlistment would also be nice. there is no specific owner there, perhaps just assume "first admin" or something like that. or a setting that set "enlistment owner" to a given user and used that user's keys.
Also related bug 1462498 tells how you could/should use a user other than 'ubuntu' for that access.