-
Notifications
You must be signed in to change notification settings - Fork 30
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 2031854: Add e2e test to 4.9 branch #71
Bug 2031854: Add e2e test to 4.9 branch #71
Conversation
@dagrayvid: This pull request references Bugzilla bug 2031854, which is invalid:
Comment In 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dagrayvid 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 |
/uncc @jmencak |
/bugzilla refresh |
@dagrayvid: This pull request references Bugzilla bug 2031854, 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. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
thanks @dagrayvid , /lgtm Backport risk assessement
/label backport-risk-assessed |
/cherry-pick release-4.8 |
@dagrayvid: once the present PR merges, I will cherry-pick it on top of release-4.8 in a new PR and assign it to you. In 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. |
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
/label cherry-pick-approved |
@dagrayvid: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@dagrayvid: All pull requests linked via external trackers have merged: Bugzilla bug 2031854 has been moved to the MODIFIED state. In 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. |
@dagrayvid: new pull request created: #72 In 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. |
In some recently published z-stream releases of OCP, the driver-toolkit image contained the wrong kernel package versions. One measure we can take to avoid this going forward is to run an e2e test script against each nightly build of OCP to confirm the correct package versions are being installed.
We have been running this test as a periodic, using the e2e test from the master branch. To simplify the ci-operator configs for the driver-toolkit tests when adding them as release informing jobs, we should backport the e2e test to each branch we are testing against.