status-cortx-cloud.sh was checking the total count of consul pods against the sum of expected server pods (max(3, #worker-nodes)) and expected client pods. However, the expected number is based on the number of worker nodes not tainted w/ NoSchedule. This does not work as expected when a node that is normally a worker node is tainted with NoSchedule.
To fix I have stopped checking for the expected number of cortx-consul-client pods, and only count cortx-consul-server pods. This is not a useful check anyway.
Type of change
[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates
Applicable issues
This change fixes an issue: CORTX-34284
CORTX image version requirements
NA
How was this tested?
Manual test: deploy cluster, taint one node, run status check... confirm that all pass
Also test with node not tainted to ensure that normal case passes, too.
Checklist
[x] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
Description
status-cortx-cloud.sh was checking the total count of consul pods against the sum of expected server pods (max(3, #worker-nodes)) and expected client pods. However, the expected number is based on the number of worker nodes not tainted w/ NoSchedule. This does not work as expected when a node that is normally a worker node is tainted with NoSchedule.
To fix I have stopped checking for the expected number of cortx-consul-client pods, and only count cortx-consul-server pods. This is not a useful check anyway.
Type of change
Applicable issues
CORTX image version requirements
NA
How was this tested?
Manual test: deploy cluster, taint one node, run status check... confirm that all pass Also test with node not tainted to ensure that normal case passes, too.
Checklist
If this change requires newer CORTX or third party image versions:
imagefields in solution.example.yaml have been updated to use the required versions.appVersionfield of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:)