Bug 1401103

Summary:	Unable to set retirement date for Stacks
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	UI - OPS	Assignee:	lgalis
Status:	CLOSED ERRATA	QA Contact:	Niyaz Akhtar Ansari <nansari>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.7.0	CC:	cpelland, dajohnso, hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	retirement:stack
Fixed In Version:	5.7.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1396944	Environment:
Last Closed:	2017-02-27 19:26:23 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:	1396944
Bug Blocks:

Comment 2 CFME Bot 2017-01-09 16:11:04 UTC

New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/07ed9afb9a42fbbcba20cbbd36d1d4db7708e7c3

commit 07ed9afb9a42fbbcba20cbbd36d1d4db7708e7c3
Author:     Dan Clarizio <dclarizi>
AuthorDate: Thu Dec 1 10:55:52 2016 -0800
Commit:     Satoe Imaishi <simaishi>
CommitDate: Mon Jan 9 11:05:58 2017 -0500

    Merge pull request #12826 from lgalis/orch_stacks_retirement_from_provider_screen_error
    
    Fix retirement menu for cloud provider orchestration stacks
    (cherry picked from commit c0271f216436ccef6630f263dfcd550f5d082425)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1401103

 app/controllers/application_controller/ci_processing.rb | 6 ++++--
 app/controllers/ems_common.rb                           | 2 +-
 spec/controllers/ems_common_controller_spec.rb          | 9 +++++++++
 3 files changed, 14 insertions(+), 3 deletions(-)

Comment 3 Niyaz Akhtar Ansari 2017-01-27 08:40:12 UTC

Able to set the retirement date for stacks.
Verified in version 5.7.1.0

Comment 4 errata-xmlrpc 2017-02-27 19:26:23 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://rhn.redhat.com/errata/RHSA-2017-0320.html