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 1822564 - vmrc not working 6.7
Summary: vmrc not working 6.7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.7.4
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-09 11:03 UTC by Ondřej Ezr
Modified: 2023-10-06 19:37 UTC (History)
5 users (show)

Fixed In Version: foreman-1.24.1.27-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-30 13:12:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29439 0 Normal Closed vmrc not working 1.24 2020-11-13 17:27:11 UTC
Red Hat Product Errata RHSA-2020:4127 0 None None None 2020-09-30 13:12:21 UTC

Description Ondřej Ezr 2020-04-09 11:03:09 UTC 
https://community.theforeman.org/t/no-vmrc-after-1-24-2-upgrade/17148/6
Comment 1 Ondřej Ezr 2020-04-09 11:03:16 UTC 
Created from redmine issue https://projects.theforeman.org/issues/29439
Comment 2 Ondřej Ezr 2020-04-09 11:03:21 UTC 
Upstream bug assigned to None
Comment 5 Bryan Kearney 2020-04-09 12:02:13 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29439 has been resolved.
Comment 6 Brad Buckingham 2020-04-09 12:25:04 UTC 
Is this a regression from Satellite 6.6?
Comment 7 Ondřej Ezr 2020-04-09 13:59:57 UTC 
Yes, AFAIK it is a regression.
Comment 9 Lukáš Hellebrandt 2020-07-08 15:38:07 UTC 
Verified with Sat 6.8 snap 7.0.

1) Add a VMWare CR
2) Import a Host from that CR
3) Power On the Host
4) Hosts -> All Hosts -> <host>
5) Click Console

=> VMRC works
Comment 11 Lukáš Hellebrandt 2020-09-21 10:19:32 UTC 
James, this was a 6.8 BZ that has already been VERIFIED. Then, you flipped it to 6.7 and moved it back to ON_QA. Please, can you fix this BZ and create a proper 6.7 BZ by cloning this one?
Comment 12 James Jeffers 2020-09-21 13:28:50 UTC 
Lukas,

The new cloning procedure for z-streams indicated that this BZ was not to be cloned for 6.7.4 (neither QE not development proposed cloning after 6.7.4 z-stream triage).
Comment 13 Lukáš Hellebrandt 2020-09-21 14:50:50 UTC 
Indeed, this is a new process of verifying z-stream BZs.

Verified with Sat 6.7.4 snap 1.0 using the same steps as with 6.8 (comment 9).
Comment 18 errata-xmlrpc 2020-09-30 13:12:09 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 (Important: Satellite 6.7.4 Async Bug Fix Update), 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-2020:4127
Note You need to log in before you can comment on or make changes to this bug.