Bug 1784482

Summary: Web Console button doesn't have ID
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: aruzicka, inecas, mhulan
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_remote_execution-2.0.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Roman Plevka 2019-12-17 14:54:02 UTC
Description of problem:

<div class="btn-group">
    <a class="btn btn-default" href="/webcon/=rplevka-el7.localhost.example.com">
        Web Console
    </a>
</div>

in contrast with (e.g.) run button:

<div class="btn-group">
    <a id="run_button" class="btn btn-default" href="/job_invocations/new?host_ids%5B%5D=2">
        Schedule Remote Job
    </a>
</div>

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

Comment 3 Adam Ruzicka 2019-12-17 14:56:19 UTC
Created redmine issue https://projects.theforeman.org/issues/28526 from this bug

Comment 4 Bryan Kearney 2019-12-17 15:05:07 UTC
Upstream bug assigned to aruzicka

Comment 5 Bryan Kearney 2019-12-17 15:05:09 UTC
Upstream bug assigned to aruzicka

Comment 6 Bryan Kearney 2019-12-18 15:05:03 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28526 has been resolved.

Comment 8 Peter Ondrejka 2020-01-03 14:48:15 UTC
Verifying in sat 6.7 snap 7 per "web console", adding other missing IDs left for more coordinated effort

Comment 11 errata-xmlrpc 2020-04-14 13:28:08 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-2020:1454