Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-4629

After Adding the FIP to existing Node, The CSR get generated, It should be approved automatically.

XMLWordPrintable

    • -
    • Moderate
    • ShiftStack Sprint 232, ShiftStack Sprint 233, ShiftStack Sprint 234, ShiftStack Sprint 235, ShiftStack Sprint 236, ShiftStack Sprint 237, ShiftStack Sprint 238, ShiftStack Sprint 239, ShiftStack Sprint 240, ShiftStack Sprint 241, ShiftStack Sprint 242
    • 11
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • None
    • 3/16: telco reviewed

      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? 

       

       

            mdulko Michał Dulko
            rhn-support-shpawar SHUBHAM PAWAR
            Itshak Brown Itshak Brown
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: