Bug 1337949 - power-off confirm dialog box throws below error
Summary: power-off confirm dialog box throws below error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-20 14:09 UTC by Kedar Bidarkar
Modified: 2019-09-26 17:33 UTC (History)
3 users (show)

Fixed In Version: foreman-1.11.0.32-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:04:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15151 0 None None None 2016-05-23 20:21:13 UTC

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
Note You need to log in before you can comment on or make changes to this bug.