Red Hat Bugzilla – Bug 1608269
Uninstall the olm failed via the openshift-ansible
Last modified: 2018-10-11 03:22:29 EDT
Description of problem: Got below errors when uninstalling the olm via ansible. "Error from server (NotFound): the server could not find the requested resource (delete catalogsource-v1s.app.coreos.com tectonic-ocs)\n" Version-Release number of selected component (if applicable): openshift-ansible master branch OCP 3.11 oc v3.11.0-0.9.0 How reproducible: always Steps to Reproduce: 1, build an OCP 3.11 with the olm enabled. 2. git clone the opnshift-ansible, checkout the master branch. 3. Enable the below variables in your inventory file, and then run "ansible-playbook -i qe-inventory-host-file playbooks/olm/config.yml" command. operator_lifecycle_manager_remove=true operator_lifecycle_manager_install=false Actual results: TASK [olm : Remove tectonic-ocs CatalogSource-v1 manifest] ******************************************************************************************************************************************************** Wednesday 25 July 2018 15:52:50 +0800 (0:00:02.068) 0:01:09.365 ******** ... fatal: [qe-jiazha-311master-etcd-1.0724-q2x.qe.rhcloud.com]: FAILED! => {"changed": false, "msg": {"cmd": "/usr/bin/oc delete CatalogSource-v1 tectonic-ocs -n operator-lifecycle-manager", "results": {}, "returncode": 1, "stderr": "Error from server (NotFound): the server could not find the requested resource (delete catalogsource-v1s.app.coreos.com tectonic-ocs)\n", "stdout": ""}} Before the uninstalling, the "tectonic-ocs" did exist, I think we should put this removing before the CRD removing. Expected results: The olm can be uninstalled success via ansible. Additional info:
I submit a PR https://github.com/openshift/openshift-ansible/pull/9334 to fix this issue, looking for your comments.
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/4ebcca070039324e91140ffe2c3617898cf7b6f8 fix bug 1608269 https://github.com/openshift/openshift-ansible/commit/ac61a4e4d0d202271537925047aecdc702451a33 Merge pull request #9334 from jianzhangbjz/bug-1608269 fix bug 1608269
Fix is available in openshift-ansible-3.11.0-0.13.0
Remove the Depends on 1615191 since I can install the OLM separately. Set below variable in the inventory file: operator_lifecycle_manager_remove=true operator_lifecycle_manager_install=false And then, run: [jzhang@localhost openshift-ansible]$ ansible-playbook -i qe-inventory-host-file playbooks/olm/config.yml Success, but the namespace was NOT deleted. Verify failed. [root@qe-jiazha-round3master-etcd-1 ~]# oc get all -n operator-lifecycle-manager No resources found. [root@qe-jiazha-round3master-etcd-1 ~]# oc get ns | grep operator operator-lifecycle-manager Active 3h Verify failed and I file a PR(https://github.com/openshift/openshift-ansible/pull/9599) to fix this. Please have a review!
Thanks for the PR, merged in master
Fix is available in openshift-ansible-3.11.0-0.16.0
I used the openshift-ansible-3.11.0-0.16.0 branch to test it, LGTM, verify it.
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/RHBA-2018:2652