-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.10.z
-
?
-
Moderate
-
No
-
Rejected
-
False
-
-
Release Note Not Required
-
-
3/16: telco reviewed
This is a clone of issue OCPBUGS-4629. The following is the description of the original issue:
—
Description of problem:
Platform: RedHat Openstack
After adding FIP to the nodes, The CSR will generate and not get approved automatically, It stays in a pending state. It should be approved automatically.
Version-Release number of selected component (if applicable):
4.10.40
How reproducible:
Steps to Reproduce:
1. Deploy Cluster on RedHat OpenStack Platform 2. Once all nodes are in Ready state, Add the FIP from Openstack Console. 3. Observe the Newly Generated CSR's.
Actual results:
The CSR will get generated after adding extra FIP.
Expected results:
The Newly Generated CSR should approved and issued automatically.
Additional info:
We found the Older BUG: https://bugzilla.redhat.com/show_bug.cgi?id=1860774 As per comment #32, The fix is available but its only tested on VMWare.
If the BUG is a duplicate, Then could we validate it once on the Openstack platform as well?
- blocks
-
OCPBUGS-19460 After Adding the FIP to existing Node, The CSR get generated, It should be approved automatically.
- Closed
- clones
-
OCPBUGS-4629 After Adding the FIP to existing Node, The CSR get generated, It should be approved automatically.
- Closed
- is blocked by
-
OCPBUGS-4629 After Adding the FIP to existing Node, The CSR get generated, It should be approved automatically.
- Closed
- is cloned by
-
OCPBUGS-19460 After Adding the FIP to existing Node, The CSR get generated, It should be approved automatically.
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update