-
Notifications
You must be signed in to change notification settings - Fork 288
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
read failureReason and failureMessage from the vsphereVM object to the vspheremachine #833
read failureReason and failureMessage from the vsphereVM object to the vspheremachine #833
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yastij 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 |
c707d04
to
feb701a
Compare
feb701a
to
e0334bc
Compare
0a12aaf
to
22dae9c
Compare
…e vspheremachine Signed-off-by: Yassine TIJANI <ytijani@vmware.com> Co-authored-by: Naadir Jeewa <jeewan@vmware.com>
22dae9c
to
2bae906
Compare
/lgtm Hi @yastij, Holding in case anyone else wants to make a final pass. |
/hold cancel |
What this PR does / why we need it: This PR ensures that we set the machines as failed when they are deleted from vcenter directly. remediation should happen through
MachineHealthChecks
Which issue(s) this PR fixes : Fixes #805
Special notes for your reviewer:
/cc @akutz @randomvariable
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note: