Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing upgrade mirror suite #4417

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

AmarnatReddy
Copy link
Contributor

Description

Fixing upgrade mirror suite

Problem:
Recently, we introduced test cases to evaluate the performance of mirroring in both the current and upgraded builds. During these tests, we remove the mirror setup, which leads to issues when validating the status after the upgrade.

Solution:
To resolve this, we have repositioned the test case that collects mirror statistics to the beginning of the process. Now, we first gather the initial stats, then configure the mirror, proceed with the upgrade, and finally collect the mirror stats again post-upgrade. This ensures a more accurate validation of the mirroring functionality.

Logs : http://magna002.ceph.redhat.com/cephci-jenkins/cephci-run-O3YF8K/

Failed Log : http://magna002.ceph.redhat.com/cephci-jenkins/results/openstack/IBM/8.0/rhel-9/Upgrade/19.2.0-58/54/tier-0_cephfs_mirrror_upgrade_ibm_6x_to_8x/

Please include Automation development guidelines. Source of Test case - New Feature/Regression Test/Close loop of customer BZs

click to expand checklist
  • Create a test case in Polarion reviewed and approved.
  • Create a design/automation approach doc. Optional for tests with similar tests already automated.
  • Review the automation design
  • Implement the test script and perform test runs
  • Submit PR for code review and approve
  • Update Polarion Test with Automation script details and update automation fields
  • If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

Copy link
Contributor

@Manimaran-MM Manimaran-MM left a comment

Choose a reason for hiding this comment

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

LGTM

Signed-off-by: Amarnath K <[email protected]>
Copy link
Contributor

@Manimaran-MM Manimaran-MM left a comment

Choose a reason for hiding this comment

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

LGTM

@openshift-ci openshift-ci bot added the lgtm Add this label when the PR is good to be merged label Feb 11, 2025
Copy link
Contributor

openshift-ci bot commented Feb 11, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AmarnatReddy, Manimaran-MM

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergify mergify bot merged commit 9f5ae0e into red-hat-storage:main Feb 11, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Add this label when the PR is good to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants