-
Notifications
You must be signed in to change notification settings - Fork 8
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
Two Remediations and Taint Addition for E2E #62
Conversation
razo7
commented
Jul 2, 2023
- Reorganize FAR E2E test code for testing two FAR creation, one following another, to two different nodes.
- Test the addition of FAR taint prior to checking the pod's logs and the node's boot time
Skipping CI for Draft Pull Request. |
/test ? |
@mshitrit: The following commands are available to trigger required jobs:
Use 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. |
/test 4.13-openshift-e2e |
/test 4.13-openshift-e2e |
Stress the cluster with one after another FAR CRs, and watch if they succeed
/test 4.13-openshift-e2e |
1 similar comment
/test 4.13-openshift-e2e |
Is it expected to have two commits with the same name? (also there's a little typo "reoboot") |
Add wasFarTaintAdded to check if the node has FAR taint prior to checking the pod's logs and the node's boot time
We randomize using the current time as seed and we store the old node name so we won't create new CR for the same node on the second test
/test 4.13-openshift-e2e |
The random number was not been used to select the worker node
/test 4.13-openshift-e2e |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7, slintes 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 |