Description of problem: Service catalog playbook (/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/service-catalog.yml) fails if the namespace no longer exists. TASK [ansible_service_broker : remove ansible-service-broker service] ************************************************************************************************************************************** fatal: [master1]: FAILED! => {"changed": false, "msg": {"cmd": "/usr/local/bin/oc get service asb -o json -n openshift-ansible-service-broker", "results": [{}], "returncode": 1, "stderr": "Error from server (NotFound): namespaces \"openshift-ansible-service-broker\" not found\n", "stdout": ""}} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/service-catalog.retry Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: TASK [ansible_service_broker : remove ansible-service-broker service] ************************************************************************************************************************************** fatal: [master1]: FAILED! => {"changed": false, "msg": {"cmd": "/usr/local/bin/oc get service asb -o json -n openshift-ansible-service-broker", "results": [{}], "returncode": 1, "stderr": "Error from server (NotFound): namespaces \"openshift-ansible-service-broker\" not found\n", "stdout": ""}} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/service-catalog.retry Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag
-- rpm -q openshift-ansible openshift-ansible-3.7.23-1.git.0.bc406aa.el7.noarch -- rpm -q ansible ansible-2.4.2.0-2.el7.noarch -- ansible --version ansible 2.4.2.0 config file = /root/.ansible.cfg configured module search path = [u'/usr/share/ansible'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]
This might need to be reset to the installer component again, I just didn't know how to otherwise get this triaged to the right group.
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1523294 This can be worked around by setting ansible_service_broker_remove=false in the inventory if the broker is not deployed. I'm not sure this is severe enough for a backport, so I think we should mention the workaround and close this in favor of the 3.10 aligned bug. Is this acceptable?
Scott, can we align this to 3.9.z?
Yes, 3.9.z is fine after we confirm the fix on master.
https://github.com/openshift/openshift-ansible/pull/8270
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/ae7d8b890ccd4244b4a0a9d7783b63be4658b973 Bug 1561485- get now returns empty instead of error when the namespace is missing https://github.com/openshift/openshift-ansible/commit/2681fa47c5c9579c9a552ca48a32b8d7988ed258 Merge pull request #8270 from fabianvf/bz1561485 Bug 1561485- get now returns empty instead of error when the namespace is missing
https://github.com/openshift/openshift-ansible/pull/8396 3.9 backport
image is ready ,change it to ON_QA
verified in v3.10 and v3.9 openshift-ansible-3.10.0-0.53.0 openshift-ansible-3.9.30-1 TASK [ansible_service_broker : remove ansible-service-broker service] ************* Monday 28 May 2018 06:49:25 +0000 (0:00:01.576) 0:01:40.802 ************ ok: [*****.com]
I'm facing performance issues in client with openshift 3.9.27, deployed in 5 nodes (1x master, 1x infra, 3x nodes - rhel 7.5 x86_64). When we try to remove any project, pod, containers some objects stuck in status "Terminating" even if try force remove or reboot node, nothing changed. I'm facing the same issue in customer, case: - https://access.redhat.com/support/cases/#/case/02139285
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:1816