Update existing VM keypair

Bug #1771589 reported by Tobias Rydberg
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Public Cloud WG
Fix Released
Jean-Daniel Bonnetot

Bug Description

Update keys rather than delete and then create with the same name again which will cause temporary outage.

"There are some issues with updating existing keypairs, such as leading a user to think that the updated keypair will be injected into the existing guest VM, which it won't. We also don't have a PUT on flavors for similar reasons.

(mriedem): 2017-09-28: see topics discussed for Queens: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122566.html - need end user/operator feedback on direction here

(mriedem): 2017-11-08: Related ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123071.html"

Related: https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/rebuild-keypair-reset.html

Changed in openstack-publiccloud-wg:
importance: Undecided → High
Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Tobias Rydberg (tobberydberg) wrote :

Jean-Daniel, I'm changing the status to "implemented" for this one.

Changed in openstack-publiccloud-wg:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers