-
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
Add Events for far Remediation Process #107
Conversation
Skipping CI for Draft Pull Request. |
8702f48
to
9ae463a
Compare
9ae463a
to
de82ba3
Compare
/test 4.14-openshift-e2e |
/test 4.15-openshift-e2e |
/test 4.14-openshift-e2e |
/test 4.15-openshift-e2e |
May I ask you to wait for #106 before merging this? Many events come from the fence agent execution that is reworked in that PR. |
44d53fc
to
554ff4d
Compare
72b231b
to
8d6e826
Compare
/test 4.14-openshift-e2e |
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 left some comments
a1df012
to
75e88ae
Compare
/test 4.14-openshift-e2e |
/test 4.14-openshift-e2e |
/test 4.14-openshift-e2e |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clobrano, razo7 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 |
6fc35f6
to
e4a7bbf
Compare
Use Medik8s shared events
The events will help to identify the remediation process by looking on far CR events
… process The events will help to identify the remediation process by looking on node events. Fetch node from IsNodeNameValid, and whether taint was added by AppendTaint
IsNodeNameValid is no longer needed, as we no longer only need to check CR node validty but we want to receive the node object as well on success
s/CreateFARRemediationTaint/CreateRemediationTaint. Look for the actual errors, so we can catch a change in the actual errors from the UTs
Use human readable timing for timeouts with even better var names. Use verifyPreRemediationSucceed that include checking for finalizer and taint (from event and value). Sleep for a second between unit tests to give dummy reconcilation to run first.
Decouple test
e4a7bbf
to
34ce0ee
Compare
/lgtm |
To ease the tracking of the remediation process of far custom resource we add events to indicate major milestones (such as fencing, workload deletion, etc.)
GetNodeWithName
instead ofIsNodeNameValid
which is no longer needed.ECOPROJECT-1663