Compute v2 Keypair has name_attribute and name
Bug #1422041 reported by
Brian Curtin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack SDK |
Fix Released
|
High
|
Terry Howe | ||
Bug Description
Keypair specifies fingerprint as its name_attribute, yet it sets an explicit name property which makes sense given that Keypairs have an actual name. The name_attribute should be removed.
| description: | updated |
Revision history for this message
| Terry Howe (thowe-g) wrote | #1 |
| Changed in python-openstacksdk: | |
| assignee: | nobody → Terry Howe (thowe-g) |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-openstacksdk (master) | #2 |
| Changed in python-openstacksdk: | |
| status: | Confirmed → In Progress |
| Changed in python-openstacksdk: | |
| milestone: | none → halfliberty |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-openstacksdk (master) | #3 |
| Changed in python-openstacksdk: | |
| status: | In Progress → Fix Committed |
| Changed in python-openstacksdk: | |
| importance: | Undecided → High |
| milestone: | none → 0.6 |
| tags: | added: resource |
| Changed in python-openstacksdk: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Okay, little bit of a weird situation here for sure. It has name as the id_attribute and fingerprint as the name because keypairs are keyed on name, but the fingerprint makes a good way to identify one. If anything, they should be reversed, but it shoud *not* be removed.