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

fail to upgrade osus from 5.0.2 to 5.0.3: required metadataURI

XMLWordPrintable

    • Important
    • No
    • 2
    • OTA 254, OTA 255, OTA 257
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

          The osus upgrade from 5.0.2 to 5.0.3 stuck due to 5.0.3 csv is pending on requirements.
      
      # ./oc -n openshift-update-service get ip
      NAME            CSV                              APPROVAL   APPROVED
      install-kxm9q   update-service-operator.v5.0.2   Manual     true
      install-wpgw2   update-service-operator.v5.0.3   Manual     true
      
      # ./oc -n openshift-update-service get csv
      NAME                             DISPLAY                    VERSION   REPLACES                         PHASE
      update-service-operator.v5.0.2   OpenShift Update Service   5.0.2     update-service-operator.v5.0.1   Replacing
      update-service-operator.v5.0.3   OpenShift Update Service   5.0.3     update-service-operator.v5.0.2   Pending
      
      # ./oc -n openshift-update-service get csv update-service-operator.v5.0.3 -ojson|jq .status
      {
        "cleanup": {},
        "conditions": [
          {
            "lastTransitionTime": "2024-05-20T07:04:46Z",
            "lastUpdateTime": "2024-05-20T07:04:46Z",
            "message": "requirements not yet checked",
            "phase": "Pending",
            "reason": "RequirementsUnknown"
          },
          {
            "lastTransitionTime": "2024-05-20T07:04:46Z",
            "lastUpdateTime": "2024-05-20T07:04:46Z",
            "message": "one or more requirements couldn't be found",
            "phase": "Pending",
            "reason": "RequirementsNotMet"
          }
        ],
        "lastTransitionTime": "2024-05-20T07:04:46Z",
        "lastUpdateTime": "2024-05-20T07:04:46Z",
        "message": "one or more requirements couldn't be found",
        "phase": "Pending",
        "reason": "RequirementsNotMet",
        "requirementStatus": [
          {
            "group": "apiextensions.k8s.io",
            "kind": "CustomResourceDefinition",
            "message": "CRD installed alongside other CSV(s): update-service-operator.v5.0.2",
            "name": "updateservices.updateservice.operator.openshift.io",
            "status": "PresentNotSatisfied",
            "version": "v1"
          },
          {
            "group": "",
            "kind": "ServiceAccount",
            "message": "Service account is owned by another ClusterServiceVersion",
            "name": "updateservice-operator",
            "status": "PresentNotSatisfied",
            "version": "v1"
          }
        ]
      }
      
      # ./oc -n openshift-update-service get ip install-wpgw2 -ojson|jq .status.conditions
      [
        {
          "lastTransitionTime": "2024-05-20T07:05:46Z",
          "lastUpdateTime": "2024-05-20T07:05:46Z",
          "message": "error validating existing CRs against new CRD's schema for \"updateservices.updateservice.operator.openshift.io\": error validating updateservice.operator.openshift.io/v1, Kind=UpdateService \"openshift-update-service/sample\": updated validation is too restrictive: [].status.metadataURI: Required value",
          "reason": "InstallComponentFailed",
          "status": "False",
          "type": "Installed"
        }
      ]

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

      cincinnati-operator-bundle-container-v5.0.3-4
      cincinnati-operator-container-v5.0.3-5
      cincinnati-container-v5.0.3-5

      How reproducible:

          always

      Steps to Reproduce:

          1. Install osus 5.0.2 on ocp cluster 4.16
          2. Approve the 5.0.3 ip manually 
          3.
          

      Actual results:

          osus upgrade stuck

      Expected results:

          osus upgrade succeed

      Additional info:

          If there is not osus instance created, the operator could be upgraded from 5.0.2 to 5.0.3 successfully. upgrade osus from 5.0.1 to 5.0.2 also works well.

              trking W. Trevor King
              rhn-support-jiajliu Jia Liu
              Jia Liu Jia Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: