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

Deploying spoke cluster with wrong hub cluster, fails deploy with right hub cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Undefined Undefined
    • None
    • 4.12
    • Telco Performance
    • None
    • Moderate
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Hub cluster kni-qe10 is defined in the ZTP siteconfig manifest of the spoke cluster helix05.
      When invoking deploy using a different hub cluster, kni-qe-19 , for this spoke helix05, the deploy fails.
      But then invoking the deploy with kn-qe10, the right hub cluster, also fails.

       

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      Invoke ZTP deploy with a hub-cluster different from the one defined in the spoke manifest. the invoke the deploy again with the hub cluster that appears in the manifest. 

       

      Steps to Reproduce:

      1. Invoked Jenkins job with wrong hub cluster, kni-qe19 for spoke helix05, console log attached: https://drive.google.com/file/d/1N6mSwpiDcgZqT6lBSfIsDsp4B3OY4QzS/view?usp=sharing
      2. Invoke Jenkins job with right hub cluster, kni-qe10 for spoke helix05, console log attached: https://drive.google.com/file/d/1lJlqt7jo3oPeAQeFXZsvRen3mTHJ-lvU/view?usp=sharing

      Actual results:

      Timeout in ZTP pipeline at ansible task: deploy-gitops-du : wait for gitops clusters and policies apps to be in sync
      
      Due to failed to get this:
      oc -n openshift-gitops get apps clusters -o json | jq -r '.status.sync.status'

      Expected results:

      Status should be Synced before timeout

      Additional info:

       

            rhn-support-nwaizer Niv Gal Waizer (Inactive)
            rhn-support-nwaizer Niv Gal Waizer (Inactive)
            Ofer Bochan Ofer Bochan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: