Description of problem: After the upgrade of all the pods is performed, the upgrade playbook should check the health of the heketi and glusterblock provisioner pod and only then pass the playbook run. It should fail if all OCS pods are unhealthy. Version-Release number of selected component (if applicable): OCS 3.11 How reproducible: always Steps to Reproduce: 1. Deploy a cluster to be upgraded. 2. Run IOs on the cluster before performing an upgrade using the upgrade playbook. 3. Run the upgrade playbook, # ansible-playbook -i <inv_file> /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml 4. If the health of heketi and glusterblock provisioner pod is not 1/1 and Running state, the playbook should fail. 5. If the health of heketi and glusterblock provisioner pod is 1/1 and Running state, the playbook should pass. Actual results: The upgrade playbook doesn't check the heketi and glusterblock provisisoner pod health once upgrading successfully. Expected results: The upgrade playbook should check the heketi and glusterblock provisisoner pod health once upgrading successfully.
This is already taken care of. heketi: https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_storage_glusterfs/tasks/heketi_deploy.yml#L58-L70 glusterblock-provisioner: https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_storage_glusterfs/tasks/glusterblock_deploy.yml#L28-L40 Both tasks do not succeed until a pod is found that is "Ready". Closing this as NOTABUG.