Bug 1384515

Summary:	VMware Shutdown Guest from Suspended
Product:	Red Hat CloudForms Management Engine	Reporter:	Leo Khomenko <lkhomenk>
Component:	UI - OPS	Assignee:	Roman Blanco <rblanco>
Status:	CLOSED WONTFIX	QA Contact:	Dave Johnson <dajohnso>
Severity:	low	Docs Contact:
Priority:	medium
Version:	5.7.0	CC:	dajohnso, hkataria, jfrey, jhardy, mpovolny, obarenbo
Target Milestone:	GA	Flags:	lkhomenk: automate_bug+
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	vsphere:power
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-02 14:29:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	VMware	Target Upstream Version:

Description Leo Khomenko 2016-10-13 12:55:39 UTC

Description of problem:"Shutdown Guest" is available from Details menu of VM from Suspended state even if VM Tools were not installed(toolsNotInstalled)


Version-Release number of selected component (if applicable):5.7.0.4


How reproducible:always


Steps to Reproduce:
1.open details menu of suspended VM on vsphere
2.check available Power options
3.

Actual results:"Shutdown Guest" is displayed (but not working - "The attempted operation cannot be performed in the current state (Suspended)."


Expected results:"Shutdown Guest" isn't displayed 


Additional info:this appeared in 5.7. It's known that Power Action in Details menu are filtered, and we are able to perform only allowed operations( not like from Quadicon menu

Comment 2 Greg Blomquist 2016-10-17 19:11:37 UTC

Dan, I suspect that the page just needs to check whether or not the operation is available.  Sounds like the right error message is coming back when they try to shutdown.  So, I think that the supported operations stuff is in place here.

Set back to providers if you find otherwise.

Comment 5 Josh Carter 2018-10-02 14:29:27 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 6 Josh Carter 2018-10-02 14:32:10 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!