-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13.z, 4.14
-
No
-
Hypershift Sprint 237
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-14087. The following is the description of the original issue:
—
Description of problem:
HostedClusterConfigOperator doesn't check OperatorHub object in the Hosted Cluster. This causes that default catalogsources cannot be disabled. If there are failing catalogsources, operator deployments might be impacted.
Version-Release number of selected component (if applicable):
Any
How reproducible:
Always
Steps to Reproduce:
1. Deploy a HostedCluster 2. Connect to the hostedcluster and patch the operatorhub object: `oc --kubeconfig ./hosted-kubeadmin patch OperatorHub cluster --type json -p '[{"op": "add", "path": "/spec/disableAllDefaultSources", "value": true}]'` 3. CatalogSources objects won't be removed from the openshift-marketplace namespace.
Actual results:
CatalogSources objects are not removed from the openshift-marketplace namespace.
Expected results:
CatalogSources objects are removed from the openshift-marketplace namespace.
Additional info:
This is the code where we can see that the reconcile will create the catalogsources everytime. https://github.com/openshift/hypershift/blob/dba2e9729024ce55f4f2eba8d6ccb8801e78a022/control-plane-operator/hostedclusterconfigoperator/controllers/resources/resources.go#L1285
- clones
-
OCPBUGS-14087 HostedClusterConfigOperator doesn't check OperatorHub object in the Hosted Cluster
- Closed
- is blocked by
-
OCPBUGS-14087 HostedClusterConfigOperator doesn't check OperatorHub object in the Hosted Cluster
- Closed
- links to