-
Notifications
You must be signed in to change notification settings - Fork 52
Revert "Merge pull request #20 from alexander-demichev/annotations" #24
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
Conversation
alexander-demicev
left a comment
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
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-demichev The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@dgoodwin: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/hold We think force accepting a payload is a better solution than reverting |
|
/close |
|
@alexander-demichev: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This reverts commit 3d1c893, reversing
changes made to d4e3c4f.
The original pr in #20 looks to have broken payload delivery for the org, so per policy we need to revert as quickly as possible. Ideally you can then revert the revert, and layer in the fixed commits. However in this case the fix might be to the tests in the origin repo.
You can see whats taking down payloads here: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.10-e2e-aws-ovn-upgrade/1470831487283630080
Essentially we have tests that assert all operators hanging on the ClusterVersion must reach the correct upgrade level, and I suspect that annotation you added is to explicitly not do that, so presumably the test needs an update.
I notice you don't have any upgrade e2e jobs on this repo so that is likely how it slipped in. You may not want upgrade support so that is reasonable, but it might be good to add one just to catch this kind of thing as you are part of the payload, and that does tie you into upgrades even if your desired behavior is a little different.