-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
1
-
False
-
-
False
-
?
-
None
-
-
-
DFG Security: Test Sprint
-
1
-
Moderate
To Reproduce Steps to reproduce the behavior:
- Follow the steps in this [0] kcs article in 16.2.5+
Expected behavior
- SSH keys are successfully rotated in the undercloud and overcloud nodes
Bug impact
- Customers can not rotate the ssh key used to access overcloud nodes. This is a problem for any customer who wants to rotate keys during the lifecycle of RHOSP 16.2, but also for those who, in preparation for an FFU to 17.1, want to rotate the keys so that this activity is decoupled from the actual upgrade.
Known workaround
- Workaround is not rotating the ssh key, or rotating manually (time consuming, prone to error, and not completely documented)
Additional context
- The knowledgebase article [0] is a result of the following bz [1].
- RHOSP 17.1 introduces this process as part of tripleo-ansible, so the scope of this Jira and the associated article is 16.2 only
- It seems as if the process broke during the move from heat-admin to tripleo-admin
- The current process is failing when using 16.2.5 and 16.2.6, older z-streams were not tested
[0] https://access.redhat.com/solutions/6986397
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2025933
- is related to
-
OSPRH-14393 RHOSP 17.1 ssh key rotation process is incomplete
-
- Closed
-
There are no Sub-Tasks for this issue.