Created attachment 1618620 [details] bz reproducing steps Description of problem: kubemacpool not removed when deleting CNV Version-Release number of selected component (if applicable): kubemacpool-mac-controller-manager-6f7c4d499b-2xlmj brew/kubemacpool:v2.1.0-7 kubemacpool-mac-controller-manager-6f7c4d499b-jkrlv brew/kubemacpool:v2.1.0-7 How reproducible: always Steps to Reproduce: 1. install CNV 2. delete CNV 3. check resources Actual results: kubemacpool is the only remaining resource in openshift-cnv and consequently the ns can'be removed. see logs attached Expected results: kubemacpool removed Additional info:
How did you delete CNV? I undeployed CNV via curl -k https://pkgs.devel.redhat.com/cgit/containers/hco-bundle-registry/plain/cleanup-ds.sh?h=cnv-2.1-rhel-8 | bash -x and No MAC pool leftovers
Created attachment 1621823 [details] reproduced again
@Sebastian, can you please check?
I will take a look on this issue
I found the issue. The kubemacpool was deployed to is own namespace before so the network addons operator removed all the namespace (including the service). Now we deploy the kubemacpool in the same namespace as the network addons operator to support OLM upgrades. Create a PR to fix that issue. https://github.com/K8sNetworkPlumbingWG/kubemacpool/pull/71 With this PR we add a owner reference on the service object so when the kubemacpool manager deployment is removed the service will be also removed.
Test on OCP4.2 + CNV2.1, no kubemacpool resource left over after removing cnv $ oc get all -n openshift-cnv No resources found. QE will re-test once get an available OCP4.3 + CNV2.2 build.
Please ignore above #comment6, Fix the typo: Test on OCP4.2 + CNV2.2, no kubemacpool resource left over after removing cnv $ oc get all -n openshift-cnv No resources found. QE will re-test once get an available OCP4.3 + CNV2.2 build.
Yan, if you tested on kubemacpool version with the fix you can set this bug as verified.
Test with image container-native-virtualization-kubemacpool:v2.2.0-3
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, 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/RHEA-2020:0307