Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1816096

Summary:	[IPI OSP] destroy command loops during two days if any osp object cannot be deleted
Product:	OpenShift Container Platform	Reporter:	David Sanz <dsanzmor>
Component:	Installer	Assignee:	Mike Fedosin <mfedosin>
Installer sub component:	OpenShift on OpenStack	QA Contact:	weiwei jiang <wjiang>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	low
Priority:	medium	CC:	m.andre, mstaeble, pprinett
Version:	4.4	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-25 08:12:58 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 David Sanz 2020-03-23 10:51:27 UTC

Description of problem:

When executing openshift-install destroy command, if any object cannot be removed for any issue, command loops over the error during two days.

For example, cinder volume on failed state, unable to connect with any endpoint, etc

Version-Release number of the following components:

How reproducible:

Steps to Reproduce:
1.Install IPI on OSP
2.Make any endpoint unavailable (for example, deny connection to swift using iptables)
3.Run openshift-install destroy command

Actual results:
command loops during two days on the error deleting the object

Expected results:
command fails after some predefined time, for example, 30 minutes, also advise at the beginning of the command about the time we are going to wait, like we do on the installation process


Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Scott Dodson 2020-06-04 17:42:25 UTC

Master branch is now 4.6.0, please clone if necessary.

Comment 4 Martin André 2020-06-25 14:04:46 UTC

This is currently being worked on, there is a patch in flight.

Comment 11 Matthew Staebler 2020-11-04 18:19:02 UTC

(In reply to David Sanz from comment #0)
> When executing openshift-install destroy command, if any object cannot be
> removed for any issue, command loops over the error during two days.

The correct behavior of the destroy command is to continue to attempt to delete the resource until the user cancels the command. To me, it sounds like the incorrect behavior experienced here is not that the commands took too long to complete but rather that it completed at all.

Comment 14 Pierre Prinetti 2021-02-24 16:28:23 UTC

The philosophy here is to let the Installer run until every resource is deleted.
To avoid leaking processes in an automated environment, we suggest wrapping the DESTROY command into a "timeout" command with an appropriate value.

Comment 15 Martin André 2021-02-25 08:12:58 UTC

I assume this was re-opened when we closed the PR linked to the bug.
Closing again based on comment 14.