Trigger node deletion when machine is deleted - #1102
Conversation
thiyyakat
left a comment
There was a problem hiding this comment.
Thanks for the changes. Just two comments. PTAL.
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle rotten |
3a45864 to
9864805
Compare
|
Thanks for addressing the comments. |
|
LGTM label has been added. DetailsGit tree hash: 7c6a71242f80f6ef4851c138c0bece6fce8dbd6c |
|
/assign |
|
/lgtm |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 496d730a1f2ecd2b29ad344d0f5d0134fc5346a5 |
thiyyakat
left a comment
There was a problem hiding this comment.
Hi Gagan. I had one concern about the logs. If error can be handled differently in the callee and caller, maybe it can be improved.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
…riptions Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
Signed-off-by: Gagan163264 <gagan.surathkal@gmail.com>
0d4ef7e to
cfe75f3
Compare
|
LGTM label has been added. DetailsGit tree hash: ce3388f6ae7953dc547a6e02da2a2e7062d0e7ce |
|
Thanks for the multiple rounds of changes! /lgtm |
| return | ||
| } | ||
|
|
||
| if _, err := c.nodeLister.Get(nodeName); apierrors.IsNotFound(err) { |
There was a problem hiding this comment.
do we need this check? as in the retry function we are checking for it.
There was a problem hiding this comment.
It can serve as a short exit path, so that we do not even spawn a goroutine in case the node is not present.
What this PR does / why we need it:
"Creating machine on cloud provider"to"VM created on cloud provider. Waiting for node registration", so the status accurately reflects which stage the machine is in.Which issue(s) this PR fixes:
Fixes #1044, #1064
Tests:
Passed unit tests
Manual tests performed by deleting node manually
For #1064, machine during creation has message
Release note: