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.

Description of problem:

Having a working setup with Satellite and Compute resource (v3).

If enabling the usage of the experimental API v4 for RHEV, the console shows: Authentication failure from the Satellite


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Enable API Experimental for RHEV Compute resource
2. Select a host in Satellite and click on Console
3.

Actual results:

Fail to access the host console from Satellite

Expected results:

The console is accessible

Additional info:

Satellite 6.4
RHEV 4.2

Created redmine issue https://projects.theforeman.org/issues/25560 from this bug

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

Verified with Sat 6.7 snap 10.

When trying SPICE console, I hit same-origin policy in Firefox but that's caused by networking setup and browser security settings. VNC console works.

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-2020:1454