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

[OLMv1] fails with lots of "has unknown change, refusing to determine that change is safe" when upgrading argocd from v0.5.0 to v0.7.0

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • Rejected
    • Mewtwo Sprint 273
    • 1
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      Description of problem:

      Got the below errors when upgrading argocd to v0.7.0 from v0.5.0.

      jiazha-mac:~ jiazha$ oc get clusterversion
      NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
      version   4.19.0-0.nightly-2025-04-10-031621   True        False         19m     Cluster version is 4.19.0-0.nightly-2025-04-10-031621
      
      jiazha-mac:~ jiazha$ oc get clusterextension
      NAME                        INSTALLED BUNDLE   VERSION   INSTALLED   PROGRESSING   AGE
      extension-argocd-operator                                False       True          2m20s
      ...
       
       - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: no bundles found for package "argocd-operator" matching version "v0.6.0"
            in channels [alpha]
          observedGeneration: 1
          reason: Failed
          status: "False"
          type: BundleDeprecated 
      
      1, Install v0.5.0
      jiazha-mac:~ jiazha$ oc get clusterextension
      NAME                        INSTALLED BUNDLE         VERSION   INSTALLED   PROGRESSING   AGE
      extension-argocd-operator   argocd-operator.v0.5.0   0.5.0     True        True          4m28s
      jiazha-mac:~ jiazha$ oc get pods
      NAME                                                 READY   STATUS    RESTARTS   AGE
      argocd-operator-controller-manager-7df86d484-dhzc9   2/2     Running   0          2m4s
      
      2, upgrade it to v0.7.0. Still get this error.
      
      jiazha-mac:~ jiazha$ oc get clusterextension extension-argocd-operator -o yaml
      apiVersion: olm.operatorframework.io/v1
      kind: ClusterExtension
      metadata:
        creationTimestamp: "2025-04-15T03:45:05Z"
        finalizers:
        - olm.operatorframework.io/cleanup-unpack-cache
        - olm.operatorframework.io/cleanup-contentmanager-cache
        generation: 3
        name: extension-argocd-operator
        resourceVersion: "35943"
        uid: 05badc8b-b67c-461d-be38-969f3182f999
      spec:
        namespace: test
        serviceAccount:
          name: argocd-operator
        source:
          catalog:
            channels:
            - alpha
            packageName: argocd-operator
            upgradeConstraintPolicy: CatalogProvided
            version: v0.7.0
          sourceType: Catalog
      status:
        conditions:
        - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: |-
            validating upgrade for CRD "argocds.argoproj.io" failed: CustomResourceDefinition argocds.argoproj.io failed upgrade safety validation. "ChangeValidator" validation failed: version "v1alpha1", field "^.status.applicationController" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.dex" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.notificationsController" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.phase" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.redis" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.repo" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.server" has unknown change, refusing to determine that change is safe
            version "v1alpha1", field "^.status.ssoConfig" has unknown change, refusing to determine that change is safe for resolved bundle "argocd-operator.v0.7.0" with version "0.7.0"
          observedGeneration: 3
          reason: Retrying
          status: "True"
          type: Progressing
        - lastTransitionTime: "2025-04-15T03:49:29Z"
          message: Installed bundle quay.io/openshift-community-operators/argocd-operator@sha256:a6fad781cf117ae2ee9d95625570e1dfbc26a10b15c099117e76c393af522cfe
            successfully
          observedGeneration: 3
          reason: Succeeded
          status: "True"
          type: Installed
        - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: ""
          observedGeneration: 3
          reason: Deprecated
          status: "False"
          type: Deprecated
        - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: ""
          observedGeneration: 3
          reason: Deprecated
          status: "False"
          type: PackageDeprecated
        - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: ""
          observedGeneration: 3
          reason: Deprecated
          status: "False"
          type: ChannelDeprecated
        - lastTransitionTime: "2025-04-15T03:45:05Z"
          message: ""
          observedGeneration: 3
          reason: Deprecated
          status: "False"
          type: BundleDeprecated
        install:
          bundle:
            name: argocd-operator.v0.5.0
            version: 0.5.0

      Actual results:

                version "v1alpha1", field "^.status.notificationsController" has unknown change, refusing to determine that change is safe

      Expected results:

      Upgrading well.

          No CRD issues.

      Additional info:

      This bug is separated from https://issues.redhat.com/browse/OCPBUGS-53019 

          

              anik120 Anik Bhattacharjee
              rhn-support-jiazha Jian Zhang
              None
              None
              Jian Zhang Jian Zhang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: