Description of problem: ConfigMaps leftovers are seen in the namespace after a SpecialResource ( configmaps based ) is deleted Version-Release number of selected component (if applicable): master How reproducible: Steps to Reproduce: 1. Create simple-kmod namespace 2. Create ConfigMap for simple-kmod 3. List existing configmaps in the simple-kmod namespace 3. Deploy SpecialResource for simple-kmod and wait for it to properly deploy the build and driver containers. 5. Delete SpecialResource for simple-kmod 6. Check the namespace configmaps Actual results: Extra configmaps ( with prefix: sh.helm. ) can be seen in the namespace that were not present before deploying the simple-kmod specialresource # oc get cm -n simple-kmod NAME DATA AGE kube-root-ca.crt 1 13m openshift-service-ca.crt 1 13m sh.helm.hooks.post-install 0 11m sh.helm.hooks.pre-install 0 13m sh.helm.release.v1.simple-kmod.v1 1 13m simple-kmod-chart 2 13m Expected results: Configmaps in the namespace to be the same as before specialresource deployment: # oc get cm -n simple-kmod NAME DATA AGE kube-root-ca.crt 1 70s openshift-service-ca.crt 1 70s simple-kmod-chart 2 7s Additional info: Same behavior can be seen for ping-pong app also.
https://github.com/openshift/special-resource-operator/pull/167
Verified this with a bundle build from Apr/25 from release-4.11 and extra configmaps are no longer seen after SpecialResource is deleted. # oc get cm NAME DATA AGE kube-root-ca.crt 1 5m19s openshift-service-ca.crt 1 5m19s sh.helm.hooks.post-install 0 4m21s sh.helm.hooks.pre-install 0 4m21s simple-kmod-chart 2 5m9s simple-kmod-driver-build-e383247e62b56585-1-ca 1 4m13s simple-kmod-driver-build-e383247e62b56585-1-global-ca 1 4m13s simple-kmod-driver-build-e383247e62b56585-1-sys-config 1 4m13s # oc delete -f charts/simple-kmod-0.0.1/simple-kmod-configmap.yaml specialresource.sro.openshift.io "simple-kmod" deleted # oc get cm NAME DATA AGE kube-root-ca.crt 1 5m46s openshift-service-ca.crt 1 5m46s simple-kmod-chart 2 5m36s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069