Keypair update returns unclear error with invalid name

Bug #1144839 reported by Scott Devoid
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
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.

Chuck Short (zulcss)
Changed in nova:
status: New → Opinion
Revision history for this message
Scott Devoid (scott-devoid) wrote :

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.

summary: - Keypair name restrictions needed?
+ Keypair update returns unclear error with invalid name
Changed in nova:
status: Opinion → New
description: updated
Revision history for this message
Brant Knudson (blk-u) wrote :
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Scott Devoid (scott-devoid) wrote :

I can confirm that the error text is now more descriptive:
ERROR: Keypair data is invalid: Keypair name contains unsafe characters

Changed in nova:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers