-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
After setting `cronjob` to unmanaged, the cronjob still be recreated by CVO.
MacBook-Pro:~ jianzhang$ oc patch clusterversion version --type=merge -p '{"spec": {"overrides":[{"kind": "cronjob", "name": "collect-profiles", "namespace": "openshift-operator-lifecycle-manager", "unmanaged": true, "group": "batch"}]}}'
clusterversion.config.openshift.io/version patched
MacBook-Pro:~ jianzhang$ oc project
Using project "openshift-operator-lifecycle-manager" on server "https://api.wewang-azure.qemag.azure.devcluster.openshift.com:6443".
MacBook-Pro:~ jianzhang$ oc delete cronjob collect-profiles
cronjob.batch "collect-profiles" deleted
MacBook-Pro:~ jianzhang$ oc get cronjob
NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE
collect-profiles */15 * * * * False 0 <none> 36s
Version-Release number of selected component (if applicable):
oc get clusterversion -o jsonpath='{.status.desired.image}{"\n"}' version registry.ci.openshift.org/ocp/release@sha256:0eb443da80d35fbd41591f2fbfe74fe9359c80ae02f2c0c0e09c9a4dc335748f
How reproducible:
always
Steps to Reproduce:
1. Set the Cronjob kind to unmanaged.
MacBook-Pro:~ jianzhang$ oc patch clusterversion version --type=merge -p '{"spec": {"overrides":[{"kind": "cronjob", "name": "collect-profiles", "namespace": "openshift-operator-lifecycle-manager", "unmanaged": true, "group": "batch"}]}}'
clusterversion.config.openshift.io/version patched
MacBook-Pro:~ jianzhang$ oc get clusterversion version -o=jsonpath={.spec.overrides}
[{"group":"batch","kind":"cronjob","name":"collect-profiles","namespace":"openshift-operator-lifecycle-manager","unmanaged":true}]
2. Delete the CronJob resources.
MacBook-Pro:~ jianzhang$ oc get cronjob -n openshift-operator-lifecycle-manager
NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE
collect-profiles */15 * * * * False 0 12m 15m
MacBook-Pro:~ jianzhang$ oc delete cronjob collect-profiles -n openshift-operator-lifecycle-manager
cronjob.batch "collect-profiles" deleted
3. check if the cronjob resource recreated after a while.
Actual results:
MacBook-Pro:~ jianzhang$ oc get cronjob -n openshift-operator-lifecycle-manager NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE collect-profiles */15 * * * * False 0 7m30s 37m
Expected results:
The cronjob should not be recreated
Additional info:
MacBook-Pro:~ jianzhang$ oc get clusterversion -o jsonpath='{.status.desired.image}{"\n"}' version
registry.ci.openshift.org/ocp/release@sha256:0eb443da80d35fbd41591f2fbfe74fe9359c80ae02f2c0c0e09c9a4dc335748f
[cloud-user@preserve-olm-env2 jian]$ oc adm release extract --from=registry.ci.openshift.org/ocp/release@sha256:0eb443da80d35fbd41591f2fbfe74fe9359c80ae02f2c0c0e09c9a4dc335748f --to=release-image
...
[cloud-user@preserve-olm-env2 jian]$ ls -l release-image/ |grep cronjob
-rw-r-----. 1 cloud-user cloud-user 2047 Nov 8 01:24 0000_50_olm_07-collect-profiles.cronjob.yaml