-
Bug
-
Resolution: Done
-
Normal
-
rhos-18.0.4
-
None
-
3
-
False
-
-
False
-
?
-
rhos-ops-day1day2-upgrades
-
None
-
-
-
RHOS Upgrades 2025 Sprint 5, RHOS Upgrades 2025 Sprint 6
-
2
-
Low
Comparison greenfield deployment and adopted deployment showed that resources after adoption don't use uniquePodNames
- uniquePodNames: true + uniquePodNames: false
Adopted environment has pods as
cinder-api-0 2/2 Running 0 10d cinder-backup-0 2/2 Running 0 10d cinder-scheduler-0 2/2 Running 0 10d
when greenfield environment pods look like
cinder-5cb41-api-0 2/2 Running 6 (3d4h ago) 10d cinder-5cb41-api-1 2/2 Running 3 (9d ago) 10d cinder-5cb41-api-2 2/2 Running 1 (9d ago) 10d cinder-5cb41-backup-0 2/2 Running 0 10d cinder-5cb41-backup-1 2/2 Running 0 10d cinder-5cb41-backup-2 2/2 Running 0 10d cinder-5cb41-scheduler-0 2/2 Running 0 10d cinder-5cb41-volume-ceph-0 2/2 Running 0 10d
We should update openstackcontrolplanes templates and documentation to include `uniquePodNames`
- links to
- mentioned on
