diable-stable: keypairs with empty name behave badly

Bug #947750 reported by David Kranz on 2012-03-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Chuck Short

Bug Description

Creating a keypair with an empty name is allowed but should fail. Once such a keypair is created, it is impossible to delete it.

Fix proposed to branch: master
Review: https://review.openstack.org/5096

Changed in nova:
assignee: nobody → Chuck Short (zulcss)
status: New → In Progress
Thierry Carrez (ttx) wrote :

So does that mean it doesn't just affect diablo ?

Changed in nova:
assignee: Chuck Short (zulcss) → Brian Waldon (bcwaldon)

Reviewed: https://review.openstack.org/5096
Committed: http://github.com/openstack/nova/commit/6f67c9d043ebd104e07a59f0cd2e9eaca003a4c1
Submitter: Jenkins
Branch: master

commit 6f67c9d043ebd104e07a59f0cd2e9eaca003a4c1
Author: Chuck Short <email address hidden>
Date: Thu Mar 8 15:09:38 2012 -0500

    EC2 KeyName validation.

    According to EC2 API Documentation, the keyname
    is acccetable as a alphanumeric characters,
    spaces, dashes, and underscores.

    As well as make sure that the keyname doesnt
    exceed 255 characters.

    Make sure that the key that is being created is valid.
    Fixes bug 947750.

    Change-Id: I083af7f2cbc417150fadb79b307083bb3ba229d6
    Signed-off-by: Chuck Short <email address hidden>

Changed in nova:
status: In Progress → Fix Committed
Brian Waldon (bcwaldon) on 2012-03-10
Changed in nova:
assignee: Brian Waldon (bcwaldon) → Chuck Short (zulcss)
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers