Keypair update returns unclear error with invalid name
Bug #1144839 reported by
Scott Devoid
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Nova returns 400 error "Keypair data is invalid" if the key name contains anything outside of basic ASCII alphanumeric, "-" or "_".
-I don't see a reason for this. Our external key management system handles full unicode key names fine.-
Edit:
Updated bug status. I suggest defining a specific error "Keypair name contains invalid characters" (still 400) for more clarity.
Changed in nova: | |
status: | New → Opinion |
summary: |
- Keypair name restrictions needed? + Keypair update returns unclear error with invalid name |
Changed in nova: | |
status: | Opinion → New |
description: | updated |
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
I would suggest clarifying the error text. E.g. "Keypair name contains unallowed characters" or "Keypair public key is invalid". I spent a long time confirming that the public key was being passed in correctly when the keypair name was triggering an error.