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
encryption: switch to kube-storage-version-migrator #291
encryption: switch to kube-storage-version-migrator #291
Conversation
/retest |
a6d94b0
to
2c9c3bb
Compare
/test e2e-aws-operator |
2c9c3bb
to
ae24487
Compare
ae24487
to
da1011f
Compare
da1011f
to
8786289
Compare
8786289
to
11c60d0
Compare
/test e2e-aws-operator |
/lgtm |
11c60d0
to
0970c95
Compare
/retest |
/test e2e-aws-operator-encryption |
/test e2e-aws-operator-encryption-perf |
/retest |
2 similar comments
/retest |
/retest |
d57070f
to
1d3e069
Compare
/test e2e-aws-operator-encryption |
/retest |
2 similar comments
/retest |
/retest |
/test e2e-aws-operator-encryption |
/retest |
@vareti The failure of the e2e-aws-operator-encryption-perf doesn't appear to be infrastructure related. Is the job flakey, or is it ligit failing? |
/retest |
@marun it does not look like a infra failure. looks like a timeout from the test logs. and there is not much info in the migrator logs to check what went wrong. i am running this again to see it is flaky |
/retest |
/test e2e-aws-operator-encryption-perf |
@marun So looks like test is indeed flaky. I tried running the same test locally on my machine and it passed there too. |
Hooray, passed! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sanchezl, sttts, vareti 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 |
continuing the work done in #245
Requires https://github.com/openshift/cluster-kube-storage-version-migrator-operator to be in the release.