-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Bug 1886131: ci-operator/config/openshift/release: Drop 'abort-at=100' for e2e-44-stable-to-45-ci #12535
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
Bug 1886131: ci-operator/config/openshift/release: Drop 'abort-at=100' for e2e-44-stable-to-45-ci #12535
Conversation
…stable-to-45-ci The 4.4 -> 4.5 -> 4.4 flow was breaking on the etcd downgrade [1]. Set the environment variable to clobber the workflow default: $ git grep TEST_OPTIONS ci-operator/step-registry | grep workflow ci-operator/step-registry/openshift/upgrade/aws/loki/openshift-upgrade-aws-loki-workflow.yaml: TEST_OPTIONS: "abort-at=100" ci-operator/step-registry/openshift/upgrade/gcp/loki/openshift-upgrade-gcp-loki-workflow.yaml: TEST_OPTIONS: "abort-at=100" and avoid the rollback. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1886131
|
@wking: This pull request references Bugzilla bug 1886131, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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. |
| cluster_profile: aws | ||
| env: | ||
| TEST_OPTIONS: "" | ||
| workflow: openshift-upgrade-aws |
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.
Hrm, only the Loki workflows default to TEST_OPTIONS setting abort-at. I'm still a bit fuzzy about why this one seems to be pulling it in.
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.
I don't think that job is related - it appears to affect rollback jobs only
Nervermind, abort-at means "start rollback" not "cancel upgrade and stop". Seems it needs to be removed from the default options and be applied on rollback jobs only - #12544
|
/uncc |
|
/retest |
vrutkovs
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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, vrutkovs, wking 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 |
|
@wking: Bugzilla bug 1886131 is in an unrecognized state (CLOSED (CURRENTRELEASE)) and will not be moved to the MODIFIED state. 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. |
|
@wking: Updated the
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. |
The 4.4 -> 4.5 -> 4.4 flow was breaking on the etcd downgrade. Set the environment variable to clobber the workflow default:
and avoid the rollback.