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

HyperShift hosted cluster failed to create due to CNO timeout

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The issue was first reported by PowerVS team from IBM [~rh-ee-neyadav] (https://redhat-internal.slack.com/archives/CBN38N3MW/p1693300556265839), then investigated by [~cewong@redhat.com] (https://redhat-internal.slack.com/archives/CBN38N3MW/p1701106555174429).

When we upgrading an HyperShift operator deployment from an old version to latest release, `.spec.useMoreSecureServiceCA` is set to `false`, which added a blank line at the end of the CA bundle. This leads to CNO unable to properly set up the networking on the worker node, and subsequently the worker node cannot join the cluster.

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

      4.14

      How reproducible:

      Upgrade the HyperShift operator from an older version (no further details here) and try to launch a nightly (4.14/4.15) hosted cluster.

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      Hosted cluster stuck at rolling out cluster operators

      Expected results:

      Hosted cluster properly created.

      Additional info:

              bbennett@redhat.com Ben Bennett
              bechen@redhat.com Bear Chen
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: