Bug 1728889

Summary: Cannot retire service which has a VM that has been retired first
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvisioningAssignee: drew uhlmann <duhlmann>
Status: CLOSED ERRATA QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.4CC: duhlmann, jhardy, juwatts, nansari, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.8.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1720338 Environment:
Last Closed: 2019-08-13 08:35:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1720338    
Bug Blocks:    

Comment 3 CFME Bot 2019-07-22 20:36:03 UTC 
New commit detected on ManageIQ/manageiq/hammer:

https://github.com/ManageIQ/manageiq/commit/e8bd1a3882ab0cb25b0970545ba320cc5428a8e0
commit e8bd1a3882ab0cb25b0970545ba320cc5428a8e0
Author:     Brandon Dunne <brandondunne>
AuthorDate: Wed Jun 19 15:25:37 2019 -0400
Commit:     Brandon Dunne <brandondunne>
CommitDate: Wed Jun 19 15:25:37 2019 -0400

    Merge pull request #18895 from d-m-u/adding_already_retired_check_to_service_retire_task_create

    Don't create retirement tasks for things that are already retired

    (cherry picked from commit 6bbf5f46cd3bd36d4d2138fe2c2859afbc4c5a81)

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

 app/models/service_retire_task.rb | 1 +
 spec/models/service_retire_task_spec.rb | 9 +
 2 files changed, 10 insertions(+)
Comment 4 Niyaz Akhtar Ansari 2019-07-31 09:46:57 UTC 
Verified in Version 5.10.8.0.20190729222758_e725e22
Comment 6 errata-xmlrpc 2019-08-13 08:35:41 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/RHSA-2019:2466