Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1721888

Summary:	The VM power off/on from CR -> VMs tab, throws undefined method error 'state'
Product:	Red Hat Satellite	Reporter:	Jitendra Yejare <jyejare>
Component:	Compute Resources - GCE	Assignee:	Kavita <kgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	kgaikwad, zhunting
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.22.0.2-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:47:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1721890

Description Jitendra Yejare 2019-06-19 08:33:20 UTC

Description:
-------------------
The VM power off/on from CR -> VMs throws below error but the VM in GCE is turning on and off as expected.
Error - undefined method `state' for #Fog::Compute::Google::Server:0x005564da4bac78 Did you mean? start status

Step:
---------
1. Create/Integrate a Compute Resource of GCE in/with foreman.
2. Wait for all the VMs to be listed in VMs tab under GCE CR.
3. Click PowerOff/On button for the VM in VMs tab.

Actual Result:
----------------
The VM power off/on from CR -> VMs throws below error but the VM in GCE is turning on and off as expected.
Error - undefined method `state' for #Fog::Compute::Google::Server:0x005564da4bac78 Did you mean? start status

Expected Behavior:
--------------------
The VM Power on/off should not through any error.

Comment 1 Jitendra Yejare 2019-06-19 08:33:24 UTC

Created from redmine issue https://projects.theforeman.org/issues/26812

Comment 2 Jitendra Yejare 2019-06-19 08:33:31 UTC

Upstream bug assigned to kgaikwad

Comment 4 Bryan Kearney 2019-06-19 10:08:17 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26812 has been resolved.

Comment 5 Brad Buckingham 2019-06-21 14:28:02 UTC

*** Bug 1721887 has been marked as a duplicate of this bug. ***

Comment 8 Kavita 2019-06-28 06:37:35 UTC

Verified merge-request satellite6/foreman/merge_requests/428 which contains the commit for this BZ.

Comment 9 Jitendra Yejare 2019-07-01 11:54:23 UTC

Verified!

@Satellite 6.6 snap 9

Steps:
------------
1. Create/Integrate a Compute Resource of GCE in/with the foreman.
2. Wait for all the VMs to be listed in VMs tab under GCE CR.
3. Click PowerOff/On button for the VM in VMs tab.


Observation:
----------------
1. Error(s) (specially reported in the description of this bug) is not seen.

Comment 10 Bryan Kearney 2019-10-22 19:47:37 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/RHSA-2019:3172