You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to manually step through upgrading versions of a package using the ClusterExtension using the replaces chain in the FBC channel, moving beyond the first replaced version results in the following status condition:
- lastTransitionTime: "2024-07-03T19:44:12Z"message: 'error upgrading from currently installed version "0.1.0": no package "argocd-operator" matching version "0.3.0" in channel "alpha" found'observedGeneration: 4reason: ResolutionFailedstatus: "False"type: Resolved
In this case, I had followed the replaces chain from v0.1.0 --> v0.2.0 successfully. When attempting to go from v0.2.0 --> v0.3.0 the upgrade failed and contained the above resolution failure.
To verify this is a valid upgrade path, you can see the channel and upgrade edges with:
Once the previously created ClusterExtension is successfully installed, manually update the version to v0.2.0 (note you will have to disable the recently added CRD Upgrade Safety check for this to work due to unknown changes to argo's CRDs):
Definitely a blocker, IMO. Any idea why this is happening? My initial suspicion is that we somehow have an incorrect understanding of the currently installed version?
Definitely a blocker, IMO. Any idea why this is happening? My initial suspicion is that we somehow have an incorrect understanding of the currently installed version?
When attempting to manually step through upgrading versions of a package using the
ClusterExtension
using thereplaces
chain in the FBC channel, moving beyond the first replaced version results in the following status condition:In this case, I had followed the replaces chain from
v0.1.0
-->v0.2.0
successfully. When attempting to go fromv0.2.0
-->v0.3.0
the upgrade failed and contained the above resolution failure.To verify this is a valid upgrade path, you can see the channel and upgrade edges with:
Output
ClusterCatalog
that references the operatorhub.io catalog image:ClusterExtension
that installs theargocd-operator
atv0.1.0
:ClusterExtension
is successfully installed, manually update the version tov0.2.0
(note you will have to disable the recently added CRD Upgrade Safety check for this to work due to unknown changes to argo's CRDs):v0.3.0
:You should now be able to see the same resolution failure.
Full ClusterExtension output YAML
Just to note, this was originally found by OpenShift QE. I verified the bug was reproducible and used a different package for installation.
The text was updated successfully, but these errors were encountered: