Bug 2011089 - Machine stuck deleting after instance has been terminated and node deleted
Summary: Machine stuck deleting after instance has been terminated and node deleted
Keywords:
Status: CLOSED DUPLICATE of bug 2007802
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Joel Speed
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-05 23:20 UTC by Matt Bargenquast
Modified: 2022-04-11 08:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-08 12:04:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matt Bargenquast 2021-10-05 23:20:20 UTC
Description of problem:
A cluster has been observed in the following state:
- It has a Machine which has been in a Deleting state for several weeks.
- The Node corresponding to the Machine has been successfully deleted.
- The AWS instance associated with the Machine no longer exists.

The machine-api-controllers just repeat that they cannot find the instance:

W1005 23:05:28.413511       1 reconciler.go:450] xxxxxx-sncmc-worker-us-east-1a-t72sb: Failed to find existing instance by id i-0ca2e1f7a004dbc7f: InvalidInstanceID.NotFound: The instance ID 'i-0ca2e1f7a004dbc7f' does not exist
        status code: 400, request id: cab0c58b-c3ef-4f7c-a295-a31f2ea656cf
I1005 23:05:28.471091       1 reconciler.go:261] xxxxxx-sncmc-worker-us-east-1a-t72sb: Possible eventual-consistency discrepancy; returning an error to requeue
E1005 23:05:28.471115       1 controller.go:246] xxxxxx-sncmc-worker-us-east-1a-t72sb: failed to check if machine exists: requeue in: 20s

Version-Release number of selected component (if applicable):
4.8.11

Expected results:
The machine should be deleted if the instance no longer exists.

Comment 2 Joel Speed 2021-10-08 12:04:51 UTC
Based on the description, this appears to be a duplicate of 2007802, please let me know if you disagree and we can reopen this for further investigation

*** This bug has been marked as a duplicate of bug 2007802 ***


Note You need to log in before you can comment on or make changes to this bug.