Description of problem:
Split https://bugzilla.redhat.com/show_bug.cgi?id=1757099#c2 to this bug.
After setting the Marketplace to `Unmanaged`, it blocks the cluster upgrade.
mac:~ jianzhang$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.2.0-0.nightly-2019-10-07-203748 True True 31m Unable to apply 4.2.0-0.nightly-2019-10-08-223531: the cluster operator marketplace has not yet successfully rolled out
Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-10-07-203748
How reproducible:
always
Steps to Reproduce:
1. Install an OCP 4.2.
2. Set the Marketplace componet to `Unmanaged`.
mac:~ jianzhang$ oc get clusterversion version -o yaml|grep "overrides" -A 10
overrides:
- group: apps
kind: OperatorSource
name: redhat-operators
namespace: openshift-marketplace
unmanaged: true
- group: apps
kind: Deployment
name: marketplace-operator
namespace: openshift-marketplace
unmanaged: true
3. Upgrade the cluster
mac:~ jianzhang$ oc adm upgrade --to-image=registry.svc.ci.openshift.org/ocp/release@sha256:cf2cecc6481664ea4b11fb3524e86c8754414a746939a85be187c82f137e40ca --force=true
Actual results:
The cluster upgrading is blocked by the Marketplace component.
mac:~ jianzhang$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.2.0-0.nightly-2019-10-07-203748 True True 36m Unable to apply 4.2.0-0.nightly-2019-10-08-223531: the cluster operator marketplace has not yet successfully rolled out
Expected results:
The marketplace component should NOT block the cluster upgrading. And, any component which `Unmanaged` by cvo should NOT the cluster upgrading.
Additional info:
I'm not sure if this is a Marketplace issue or cvo issue. Report it in Marketplace component first, please feel free to transfer to the appropriate component.
Thank you for reporting this bug @jiazha
This does not appear to be a bug that the Marketplace team can address.
The Marketplace operator is managed by CVO and when it is marked as unmanaged, CVO should not update the Marketplace Operator when progressing towards a new payload.
I would agree with your assessment that CVO should not be blocked from upgrading, but that is a decision that must be made on their side, as such I will re-assign this bug to them.
(In reply to Jian Zhang from comment #3)
> Hi, Abhinav
>
> Yes, we did. Anything else we need to do for managing the marketplace
> operator?
I don't think so.