Bug 2011668

Summary:	Machine stuck in deleting phase in VMware "reconciler failed to Delete machine"
Product:	OpenShift Container Platform	Reporter:	Alex Lewis <alewis>
Component:	Cloud Compute	Assignee:	dmoiseev
Cloud Compute sub component:	Other Providers	QA Contact:	Huali Liu <huliu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	dmoiseev, musman
Version:	4.7
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Due to possible error or lag in execution of vcenter's powerOff task, machine could stuck on 'deleting' phase for quite a while. Added check for task type in deletion procedure for prevent this.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:17:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Lewis 2021-10-07 03:43:38 UTC

Description of problem:
Machine state is stuck in "deleting" when VM is powered off

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

How reproducible:
Not sure if easily reproducible.


Actual results:

The machine is stuck in deleting phase. In VMware the machine is powered off but openshift reports its powered on. Deleting the annotation on the machine "machine.openshift.io/instance-state: poweredOn" fixes the issue. Openshift should check the state from vmware not the annotation. Below is the error message in the machine events : dev1-6gbv2-storage-machineset-67w7g error: dev1-6gbv2-storage-machineset-67w7g: reconciler failed to Delete machine: The attempted operation cannot be performed in the current state (Powered on)

Expected results:

Not stuck waiting on deleting phase

Additional info:

The VM wasn't deleted manually. It was already showing Powered Off in VCenter.

So to resolve the issue, the workaround of removing the annotations from the machine YAML in OCP was followed.

Comment 16 errata-xmlrpc 2022-03-10 16:17:19 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056