-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
-
False
-
ToDo
-
0
-
0
-
Very Likely
-
0
-
Customer Escalated, Customer Facing
-
None
-
Unset
-
Unknown
-
No
Description of problem:
The following should not contain `no operators found with name oadp-operator.v1.0.2 in channel stable` error.
❯ echo 'apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
labels:
operators.coreos.com/redhat-oadp-operator.default: ""
name: redhat-oadp-operator
namespace: default
spec:
channel: stable
installPlanApproval: Manual
name: redhat-oadp-operator
source: redhat-operators
sourceNamespace: openshift-marketplace
startingCSV: oadp-operator.v1.0.2
' | oc create -f -
subscription.operators.coreos.com/redhat-oadp-operator created
~ master* 6s
❯ oc get subscription -n default redhat-oadp-operator -oyaml | yq '.status.state'
null
~ master*
❯ oc get subscription -n default redhat-oadp-operator -oyaml | yq '.status.conditions'
- lastTransitionTime: "2022-09-02T18:04:47Z"
message: all available catalogsources are healthy
reason: AllCatalogSourcesHealthy
status: "False"
type: CatalogSourcesUnhealthy
- message: 'constraints not satisfiable: no operators found with name oadp-operator.v1.0.2 in channel stable of package redhat-oadp-operator in the catalog referenced by subscription redhat-oadp-operator, subscription redhat-oadp-operator exists'
reason: ConstraintsNotSatisfiable
status: "True"
type: ResolutionFailed
Version-Release number of selected component (if applicable):
How reproducible:
everytime
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
apart from this breaking new manual installs.. it might break any generated installplans for manual upgrade to the next 1.0 version from a prior stable subscription.
Workaround is to use stable-1.0 for now.
I would expect stable to contain 1.1, 1.2, 1.x CSVs and hopefully we can also backport adding 1.0 as well to hopefully fix this issue for someone’s automated install.
