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
I have a local-storage-operator subscription that has a condition:
- message: 'constraints not satisfiable: subscription local-storage-operator requires
redhat-operator-index/openshift-marketplace/stable/local-storage-operator.v4.15.0-202410010035,
subscription local-storage-operator exists, clusterserviceversion local-storage-operator.v4.15.0-202410010035
exists and is not referenced by a subscription, @existing/openshift-local-storage//local-storage-operator.v4.15.0-202410010035
and redhat-operator-index/openshift-marketplace/stable/local-storage-operator.v4.15.0-202410010035
provide LocalVolumeDiscovery (local.storage.openshift.io/v1alpha1)'
reason: ConstraintsNotSatisfiable
status: "True"
type: ResolutionFailed
I cannot work out what that means at all. If the subscription exists and the csv exists and isn't referenced by a subscription then what is the problem? Should the csv be referenced by a subscription? The fact that it's quite clearly referenced by the local-storage-operator subscription that is showing the message is also confusing.
The text was updated successfully, but these errors were encountered:
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
I have a local-storage-operator subscription that has a condition:
I cannot work out what that means at all. If the subscription exists and the csv exists and isn't referenced by a subscription then what is the problem? Should the csv be referenced by a subscription? The fact that it's quite clearly referenced by the local-storage-operator subscription that is showing the message is also confusing.
The text was updated successfully, but these errors were encountered: