tripleo

Octavia SSH public key not updated on content/name change

Bug #1861031 reported by Carlos Goncalves
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
In Progress
Medium
Carlos Goncalves

Bug Description

A change in the desired public key is not being reflected in the Overcloud on stack update/upgrade. TripleO should replace the keypair even when the desired public key changed, i.e. its fingerprint does not match the one (possibly) already existing in the overcloud. We should compare fingerprints and replace (delete and create, no keypair update option) when they mismatch.

Original report: https://bugzilla.redhat.com/show_bug.cgi?id=1792598

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/704421

Changed in tripleo:
assignee: nobody → Carlos Goncalves (cgoncalves)
status: New → In Progress
Revision history for this message
Brent Eagles (beagles) wrote :

We need to consider the implications for running load-balancers here as well. Is it possible to push updated ssh keys to running lb vms?

Changed in tripleo:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-ansible 3.1.0

This issue was fixed in the openstack/tripleo-ansible 3.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.