← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1265563] [NEW] keypairs can not have an '@' sign in the name

 

Public bug reported:

when importing a keypair and naming the keypair like "foo@xxxxxxxxxxxx":

you get the error "Unable to import keypair."
while the message from keystone is more clear:

DEBUG:urllib3.connectionpool:"POST /v2/6ebbe9474cf84bfbb42b5962b6b7e79f/os-keypairs HTTP/1.1" 400 108
RESP: [400] CaseInsensitiveDict({'date': 'Thu, 02 Jan 2014 16:31:28 GMT', 'content-length': '108', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-86527df6-1dd6-4232-964d-0401332baa78'})
RESP BODY: {"badRequest": {"message": "Keypair data is invalid: Keypair name contains unsafe characters", "code": 400}}


message": "Keypair data is invalid: Keypair name contains unsafe characters", "code": 400}}

we should return this message or try to prevent this issue at all.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1265563

Title:
  keypairs can not have an '@' sign in the name

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  when importing a keypair and naming the keypair like
  "foo@xxxxxxxxxxxx":

  you get the error "Unable to import keypair."
  while the message from keystone is more clear:

  DEBUG:urllib3.connectionpool:"POST /v2/6ebbe9474cf84bfbb42b5962b6b7e79f/os-keypairs HTTP/1.1" 400 108
  RESP: [400] CaseInsensitiveDict({'date': 'Thu, 02 Jan 2014 16:31:28 GMT', 'content-length': '108', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-86527df6-1dd6-4232-964d-0401332baa78'})
  RESP BODY: {"badRequest": {"message": "Keypair data is invalid: Keypair name contains unsafe characters", "code": 400}}

  
  message": "Keypair data is invalid: Keypair name contains unsafe characters", "code": 400}}

  we should return this message or try to prevent this issue at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1265563/+subscriptions


Follow ups

References