-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Description of problem:
When a user upgrades MicroShift rpm's via dnf, the topolvm-controller pods are terminted and new ones created. This happens at the same time, so that there are potentially more pods than there typically are in the namespace. Greenboot expects a certain number of pods to exist, and fails when it sees more than 2, resulting in a false negative report.
Version-Release number of selected component (if applicable):
How reproducible:
80% - depending on the time it takes greenboot to check other namespaces before openshift-storage, and how long it takes to cleanup the deleted pods.
Steps to Reproduce:
1. dnf install microshift rpms + microshift-greenboot. Greenboot must be explicitly installed, since it is not a dependency of microshift. 2. start microshift 3. run 'sudo /etc/greenboot/check/required.d/40_microshift_running_check.sh' 4. Greenboot should report success 5. Upgrade or rollback microshift rpms and microshift-greenboot 6. Restart the cluster 7. run 'sudo /etc/greenboot/check/required.d/40_microshift_running_check.sh' again 8. Observe script exit status
Actual results:
The number of ready pods in the 'openshift-storage' namespace is greater than the expected '2' count. Terminating...
Expected results:
Greenboot reports success
Additional info: