Skip to content
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.

CORTX-34189 Fix status-cortx-cloud.sh regression (data-only deploy) #377

Conversation

walterlopatka
Copy link
Contributor

Description

With v0.10.0 and the introduction of potentially multiple replicas of cortx-control pods, I introduced a regression in status-cortx-cloud.sh, such that the script reported failures with a data-only deployment. This is because logic was added to account for potentially multiple replicas did not take into account a possible data-only deployment.

Along with the fix I have added a basic regression test that deploys with data-only deployment.

Type of change

  • 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-34189
  • This change is related to an issue: #

CORTX image version requirements

N/A

How was this tested?

Added new regression test that deploys with data-only deployment.
I also ran the existing regression test to confirm that standard deployment works as expected.

Checklist

  • The change is tested and works locally.
  • New or changed settings in the solution YAML are documented clearly in the README.md file.
  • [ x All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change requires newer CORTX or third party image versions:

  • The image fields in solution.example.yaml have been updated to use the required versions.
  • The appVersion field of the Helm chart has been updated to use the new CORTX version.

If this change addresses a CORTX Jira issue:

  • The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

This fixes a regression that was introduced with multi-pod
cortx-control pods.

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
@cla-bot cla-bot bot added the cla-signed label Sep 9, 2022
Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
@walterlopatka walterlopatka marked this pull request as ready for review September 9, 2022 15:38
@walterlopatka walterlopatka requested a review from a team as a code owner September 9, 2022 15:38
@@ -115,6 +115,7 @@ fi

# Check pods
expected_count=$(helm get values cortx --all --namespace "${namespace}" --output yaml | yq .control.replicaCount)
[[ ${data_deployment} == true ]] && expected_count=0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another approach would be to check the.control.enabled value, but I suppose solution.yaml should take precedence for the scripts.

@walterlopatka walterlopatka merged commit 03857f7 into Seagate:integration Sep 9, 2022
@walterlopatka walterlopatka deleted the CORTX-34189_fix_control_status branch September 9, 2022 16:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants