Bug 1427168 – unable to bring VM out of retirement from details page

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1427168 - unable to bring VM out of retirement from details page

Summary:	unable to bring VM out of retirement from details page

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	UI - OPS (Show other bugs)
Sub Component:
Version:	5.5.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	GA
Target Release:	5.7.2
Assigned To:	Roman Blanco
QA Contact:	Mike Shriver
Docs Contact:

URL:
Whiteboard:	vm:retirement
Keywords:	ZStream

Depends On:	1306471
Blocks:
	Show dependency tree / graph

Reported:	2017-02-27 08:56 EST by Satoe Imaishi
Modified:	2017-04-12 10:39 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	5.7.2.0
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1306471
Environment:
Last Closed:	2017-04-12 10:39:54 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:0898	normal	SHIPPED_LIVE	Moderate: cfme, cfme-appliance, and cfme-gemset security, bug fix, and enhancement update	2017-04-12 14:31:08 EDT

Groups: None (edit)

Comment 2 Mike Shriver 2017-04-03 11:01:23 EDT

Verified in CFME 5.7.2.0 (5.7.2.0.20170321181409_349f1b1) in Chrome, against vSphere providers.

The retirement options in the Lifecycle button are enabled for retired (non-archived/orphaned) infrastructure VMs from their details page. I was able to set a future retirement date via the Lifecycle 'Set Retirement Date' button, resuming the retired VM.

Comment 4 errata-xmlrpc 2017-04-12 10:39:54 EDT

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-2017:0898

Note You need to log in before you can comment on or make changes to this bug.