Bug 1337949

Summary:	power-off confirm dialog box throws below error
Product:	Red Hat Satellite	Reporter:	Kedar Bidarkar <kbidarka>
Component:	Compute Resources	Assignee:	Ivan Necas <inecas>
Status:	CLOSED ERRATA	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, ehelms, inecas
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.11.0.32-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:04:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kedar Bidarkar 2016-05-20 14:09:48 UTC

Description of problem:

"Are you sure you want to power off #<FogExtensions::Vsphere::MiniServer:0x0000000ec28e78>"


Version-Release number of selected component (if applicable):
sat62-snap12.1

How reproducible:


Steps to Reproduce:
1. add VMware compute resource
2. lick on the Virtual machine tab
3. select a vm anc click on "power off" 

Actual results:
"Are you sure you want to power off #<FogExtensions::Vsphere::MiniServer:0x0000000ec28e78>"

Expected results:

No such message like "#<FogExtensions::Vsphere::MiniServer:0x0000000ec28e78>"

Additional info:


No error message seen in "/var/log/foreman/production.log"

Comment 3 Ivan Necas 2016-05-23 20:18:13 UTC

Easy to fix

Comment 4 Ivan Necas 2016-05-23 20:21:11 UTC

Created redmine issue http://projects.theforeman.org/issues/15151 from this bug

Comment 5 Bryan Kearney 2016-05-24 12:17:42 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/15151 has been closed

Comment 6 Sanket Jagtap 2016-06-14 09:41:22 UTC

Build : Satellite 6.2 snap15.2

Machine was powered off and turn on without error

Comment 7 Bryan Kearney 2016-07-27 11:04:57 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-2016:1501