[2.x] maas doesn't warn/block rescue mode when user has no ssh keys
Bug #1701701 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
I commissioned a machine with "enable ssh access" selected and was unable to ssh into the machine because I didn't have any ssh keys configured for my user.
MAAS should warn or error when "enable ssh access" is selected and the user has no ssh keys.
With 2.2.0.
| summary: |
- maas doesn't warn/block commissioning with 'ssh access enabled' when - user has no ssh keys + [2.x] maas doesn't warn/block commissioning with 'ssh access enabled' + when user has no ssh keys |
| Changed in maas: | |
| milestone: | none → 2.3.0 |
| tags: | added: cdo-qa |
| Changed in maas: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: internal |
| Changed in maas: | |
| milestone: | 2.3.0 → 2.3.x |
| summary: |
- [2.x] maas doesn't warn/block commissioning with 'ssh access enabled' - when user has no ssh keys + [2.x] maas doesn't warn/block rescue mode when user has no ssh keys |
| tags: | added: cpe-onsite |
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