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

Failure to install Openshift Virtualization Operator on OCP 4.18.2 s390x cluster

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:
      Our OCP environment is version 4.18.2 installed on native LPAR's on s390x.
      The installation of the Openshift Virtualization Operator through OperatorHub will stall and never complete.

      The operator installation status will display the following indefinitely:
      Installing Operator
      The operator is being installed. This may take a few minutes.

      When checking the subscription details for kubevirt-hyperconverged, the only error that is captured by the YAML is the following:
      conditions:

      • message: 'error using catalogsource openshift-marketplace/isf-data-foundation-catalog: failed to list bundles: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 172.30.47.146:50051: connect: connection refused"'
        reason: ErrorPreventedResolution
        status: 'True'
        type: ResolutionFailed
      • lastTransitionTime: '2025-03-05T14:46:51Z'
        message: all available catalogsources are healthy
        reason: AllCatalogSourcesHealthy
        status: 'False'
        type: CatalogSourcesUnhealthy

      As stated in the above condition, we do have a catalog source called isf-data-foundation-catalog that is in a Transient_Failure state because the endpoint does not exist. But the installation of Openshift Virtualization operator has no dependency on this resource. This operator uses the “redhat-operators” for its source.

      We verified that once we deleted the failing catalog source (isf-data-foundation-catalog), the Openshift Virt operator was able to successfully install.

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

      How reproducible:
      Consistently

      Steps to Reproduce:
      1. Have an existing catalog source that is not in a Ready status.
      2. Attempt to install Openshift Virtualization Operator.
      3. Installation will never complete.

      Actual results: Openshift Virtualization Operator never completes install.

      Expected results: Openshift Virtualization Operator to complete installation even when there are catalog resource(s) that are in error state, unrelated to its requirements.

      Additional info: n/a

              ocohen@redhat.com Oren Cohen
              phchan@redhat.com Phil Chan (Inactive)
              None
              None
              Doug Slavens Doug Slavens (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: