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 1721895

Summary: The VM power off dialog shows unusual name of VM.
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: Compute Resources - GCEAssignee: Kavita <kgaikwad>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: zhunting
Target Milestone: 6.6.0Keywords: 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:50:17 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    
Attachments:
Description Flags
[Verified Screenshot] Correct VM Name on dialog none

Description Jitendra Yejare 2019-06-19 08:42:33 UTC 
Description:
-------------------
The VM power off dialog shows the unusual name of VM.

Step:
---------
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 the Power off/on the button and wait for the dialog to display for confirmation.

Actual Result:
----------------
The VM power off dialog shows the unusual name of VM.

Expected Result:
-----------------
The VM power off dialog should show an actual VM name as it is from GCE.
Comment 1 Jitendra Yejare 2019-06-19 08:42:39 UTC 
Created from redmine issue https://projects.theforeman.org/issues/26814
Comment 2 Jitendra Yejare 2019-06-19 08:42:45 UTC 
Upstream bug assigned to kgaikwad
Comment 4 Bryan Kearney 2019-06-19 10:05:17 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26814 has been resolved.
Comment 5 Jitendra Yejare 2019-06-25 11:34:32 UTC 
Testing Notes:

As per upstream PR (https://github.com/theforeman/foreman/pull/6747#issuecomment-494395694) :
This also fixes/adds More fields under GCE CR -> VM -> Details (Associated and disassociated vm).
Those fields are:  created, image.
Comment 7 Jitendra Yejare 2019-07-01 11:58:16 UTC 
Created attachment 1586250 [details]
[Verified Screenshot] Correct VM Name on dialog
Comment 8 Jitendra Yejare 2019-07-01 12:00:16 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 the Power off/on the button and wait for the dialog to display for confirmation.

Actual Result:
----------------
The VM power off dialog shows the correct name of VM now. (Screenshot is attached)
Comment 9 Bryan Kearney 2019-10-22 19:50:17 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
Comment 10 Jitendra Yejare 2020-07-10 13:49:11 UTC 
qe-test-coverage- : Minor bug, notification issue, less severity.