Description of problem: After running the upgrade playbook to upgrade OCS 3.10 to OCS 3.11 (latest available builds), the playbook passes. On checking the results of # oc get pods, the deploy-heketi pod is not terminating. The deployment had both, glusterfs and glusterfs backed registry in app-storage ns and infra-storage ns. In both the ns, deploy-heketi pods is not terminating. It's been half an hour since the pods had been deployed. Please see the describe results of these pods for more information, available as an attachment Version-Release number of selected component (if applicable): OCS 3.11 How reproducible : always Steps to Reproduce: 1. Create an OCP 3.11 + OCS 3.10 set up. Run constant block and file IOs. 2. Updated the inventory file parameters to the latest available OCS 3.11 builds. Ran the upgrade playbook, # ansible-playbook -i <inv_file> /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml 3. The upgrade playbook passes. But deploy-heketi-storage and deploy-heketi-registry-1-ndkt9 in app-storage and infra-storage respectively has not terminated. Actual results: deploy-heketi-storage and deploy-heketi-registry-1-ndkt9 in app-storage and infra-storage respectively has not terminated. Expected results: deploy-heketi-storage and deploy-heketi-registry-1-ndkt9 in app-storage and infra-storage respectively has should be terminated.
Huh... the pods shouldn't even be there to begin with! Definitely a bug.
PR is upstream: https://github.com/openshift/openshift-ansible/pull/11515
PR is merged.
Hello Jose, Can you please update the FIV for this bug ? Thanks kasturi