Merge ~ltrager/maas:enlistment_sshkeys into maas:master
Proposed by
Lee Trager
Status: | Rejected |
---|---|
Rejected by: | Blake Rouse |
Proposed branch: | ~ltrager/maas:enlistment_sshkeys |
Merge into: | maas:master |
Diff against target: |
198 lines (+89/-22) 6 files modified
src/maasserver/models/sshkey.py (+6/-1) src/maasserver/models/tests/test_sshkey.py (+15/-1) src/maasserver/testing/factory.py (+25/-0) src/metadataserver/api.py (+38/-15) src/metadataserver/tests/test_api.py (+4/-4) src/metadataserver/user_data/templates/enlistment.template (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
MAAS Lander | Approve | ||
Andres Rodriguez (community) | Needs Information | ||
Review via email: mp+353042@code.launchpad.net |
Commit message
Provide all administrator SSH keys to the enlistment environment.
When a new node enlists it does not have an owner. Previously that meant no
SSH keys were sent. If enlistment failed it was impossible to debug as there
was no way to access the system. Now the SSH keys for all administrators are
sent so any administrator can debug the problem.
To post a comment you must log in.
I’m not quite sure about this. We should talk about this. If there are many admins the keys of all of them would be here and this may change once we do rbac.