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

CASMTRIAGE-7627 ignore non-csm failed backups #655

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

jacobsalmela
Copy link
Contributor

velero_backups_check.sh causes a test failure intermittently on in-house sytems, often from other products such as PBS or Slingshot. While they may be valid failures, the CSM product is not at fault, so those should not trigger a test failure.

for this commit, I modified it to check only for failed vault backups since that is more pertinent to CSM itself.

I moved the code that was previously run with a pipe and checking the exit code to instead make a temp file, use a single jq command to query it, and then fail if there are any failed vault backups.

if we determine other backups should be checked, we can add those to
that jq command.

@jacobsalmela jacobsalmela self-assigned this Jan 7, 2025
@jacobsalmela jacobsalmela marked this pull request as ready for review January 7, 2025 20:53
@jacobsalmela jacobsalmela force-pushed the CASMTRIAGE-7627 branch 2 times, most recently from 0733f5a to 164e86d Compare January 8, 2025 15:57
@mharding-hpe
Copy link
Contributor

/backport release/1.7

Copy link
Contributor

github-actions bot commented Jan 8, 2025

Backporting into branch release/1.7 was successful. New PR: #658

Copy link
Contributor

@kimjensen-hpe kimjensen-hpe left a comment

Choose a reason for hiding this comment

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

Consider changing the variable “failed_bakup_path” to “failed_backups_path”

`velero_backups_check.sh` causes a test failure intermittently on
in-house sytems, often from other products such as PBS or Slingshot.
While they may be valid failures, the CSM product is not at fault, so
those should not trigger a test failure.

for this commit, I modified it to check only for failed vault backups
since that is more pertinent to CSM itself.

I moved the code that was previously run with a pipe and checking the
exit code to instead make a temp file, use a single jq command to query
it, and then fail if there are any failed vault backups.

if we determine other backups should be checked, we can add those to
    that jq command.

Signed-off-by: Jacob Salmela <[email protected]>
@jacobsalmela jacobsalmela merged commit 7c81bbb into release/1.6 Jan 9, 2025
3 checks passed
@jacobsalmela jacobsalmela deleted the CASMTRIAGE-7627 branch January 9, 2025 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants