-
Notifications
You must be signed in to change notification settings - Fork 546
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
Fix crd data loss e2e test #3173
Fix crd data loss e2e test #3173
Conversation
cc5d1d1
to
f6d5239
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
blocking merge as there might be a better way to solve this |
Signed-off-by: Per Goncalves da Silva <[email protected]>
c679200
f6d5239
to
c679200
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Different approach, changing the bundle unpack timeout - which is really what this is testing now.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ankitathomas, perdasilva, tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
85d9de2
What
Fixes CRD e2e flake "blocks a CRD upgrade that could cause data loss".
Cause
The test steps involve installing a bundle, then upgrading it to a bundle with a bad crd. The install plan will retry for 60 seconds before reaching a failed state.
Fix
Applying the operatorframework.io/bundle-unpack-timeout to the OG in the test namespace to reduce the retry timeout to 5 seconds (instead of 60) leading to faster failed states
Fixes #2638