Bug 1763857

Summary:	Unable to delete container provider
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	Providers	Assignee:	Yaacov Zamir <yzamir>
Status:	CLOSED ERRATA	QA Contact:	juwatts
Severity:	high	Docs Contact:	Red Hat CloudForms Documentation <cloudforms-docs>
Priority:	medium
Version:	5.10.6	CC:	agrare, fdewaley, gekis, jfrey, jhardy, mshriver, obarenbo, simaishi, yzamir
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.10.12	Flags:	simaishi: mirror+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	5.10.12.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1733587	Environment:
Last Closed:	2019-11-06 08:58:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Container Management	Target Upstream Version:
Embargoed:
Bug Depends On:	1733587
Bug Blocks:

Comment 2 CFME Bot 2019-10-21 20:00:36 UTC

New commit detected on ManageIQ/manageiq/hammer:

https://github.com/ManageIQ/manageiq/commit/1b32f43f4b464772d4abfb4b089f4c36466bc41b
commit 1b32f43f4b464772d4abfb4b089f4c36466bc41b
Author:     Adam Grare <agrare>
AuthorDate: Tue Jul 30 09:20:52 2019 -0400
Commit:     Adam Grare <agrare>
CommitDate: Tue Jul 30 09:20:52 2019 -0400

    Merge pull request #19077 from yaacov/do-not-get-stuck-on-destroy

    Do not get stuck on destroy

    (cherry picked from commit 23750927bd53c88c249dd0c7f0abc0bc2155afaf)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1763857

 app/models/ext_management_system.rb | 7 +-
 1 file changed, 4 insertions(+), 3 deletions(-)

Comment 3 juwatts 2019-10-30 19:47:40 UTC

Verified in 5.10.12.3.20191029180220_f883bde

Successfully added and removed a container provider multiple times without failure

Comment 5 errata-xmlrpc 2019-11-06 08:58:35 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, 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/RHBA-2019:3268