argocd-operator: Operator version 0.9.0: operator image not available, Github release missing

Hi,

it seems that there is a new version, 0.9.0, of the ArgoCD operator on OperatorHub.

However, operatorhub.io is still showing 0.8.0 as the latest release. On Github, there isn’t a new release, either.

Our OpenShift cluster sees the 0.9.0 version as latest, though. When it tries to install it, the installation fails because the operator image on quay.io is missing.

The ClusterServiceVersion sets the image quay.io/argoprojlabs/argocd-operator@sha256:38d61c3acda6230525614d1e609d0955f944680ccf12c07c1c84a7e5b0b98de8.

CSV:

apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  annotations:
    operators.operatorframework.io/builder: operator-sdk-v1.10.0+git
    operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
    certified: 'false'
    olm.targetNamespaces: ''
    [...]
    capabilities: Deep Insights
    olm.operatorNamespace: openshift-operators
    containerImage: >-
      quay.io/argoprojlabs/argocd-operator@sha256:38d61c3acda6230525614d1e609d0955f944680ccf12c07c1c84a7e5b0b98de8
    categories: Integration & Delivery
    description: 'Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.'
    olm.operatorGroup: global-operators
  name: argocd-operator.v0.9.0

This image does not exist on quay.io. Maybe something went wrong during the OperatorHub release?

Screenshots

Version 0.9.0 being available via OperatorHub from the POV of our OpenShift cluster:

Bildschirmfoto 2024-04-03 um 14 40 26

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 6
  • Comments: 16 (6 by maintainers)

Most upvoted comments

hey! I released 0.9.0 and also 0.9.1 yesterday. v0.9.1 is the same as 0.9.0 except I’ve fixed the control plane issue and bumped the argocd version to 2.9.11. I have a PR open here to add it to the red hat community operators, but there’s some issue with preflight in the CI checks that causes a merge block. Currently trying to get an ETA on when that will be fixed so the PR can auto-merge, but hopefully it should be available soon!

had the same problem, my okd auto upgraded to 0.9.0 and i had a ‘jiatan75’ moment where I thought about whats going on, on operatorhub its still 0.8.0, normally operatorhub updates faster then the redhat community operator catalog, so i investigated.

this commit should have fixed it https://github.com/argoproj-labs/argocd-operator/pull/1296/files#diff-01184a8cb2250baf03253df4c205a04a94228e5db47e1cbfd7e9edf44182a65a

but https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/4321#issuecomment-2035333231 said nop because of

The PR modifies existing bundles: [‘argocd-operator/0.9.0’] (https://gist.github.com/rh-operator-bundle-bot/86fa0757b79b22cffbfd9003c7b97bc8)

so I think what needs to be done is to release a 0.9.1 csv over here in the argocd operator repo then update or create a new pr with 0.9.1 in community-operators-prod repo

Unfortunately, we had automatic update enabled on our OKD cluster and the process failed. The service is up and running, but 0.8.0 stuck in “Replacing” status while 0.9.0 cannot start up and logs an error message continuously:

9 times in the last 0 minutes
install strategy failed: Deployment.apps "argocd-operator-controller-manager" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"control-plane":"argocd-operator"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

I was able to reproduce it just now, running ArgoCD on a Single Node OKD environment. This might be the reason why the new version is deleted on operatorhub.io.

hello! Yep currently trying to fix this, but I wanted to verify everything with my teammate first… unfortunately he’s on PTO until wednesday. In our release document, it didn’t explicitly state that the community operators release PR should be merged before the RH operators PR, so I made both PR’s at the same time, and it was caught in the community-operators merge checks that the labels are wrong (due to an automatic change with some control-plane labels that is made every time we run make bundle), but the RH operators PR had already done an auto-merge. We don’t usually do z-stream releases (like 0.9.1 would be), although we have already been considering starting to in order to keep up with argo cd patch updates. Once my teammate is back on wednesday I’ll work with him to sort out this whole situation, but if there is a more dire need to have it done before hand please let me know, and sorry for all the confusion!