Bug 1806196

Summary: Click on Hosts -> Audits render json result
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: Audit LogAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.7.0CC: inecas, oprazak
Target Milestone: 6.7.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Fixed In Version: foreman- Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:54 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:

Description Ranjan Kumar 2020-02-22 19:38:06 UTC
Description of problem: Audits button in Host page renders JSON result. it should redirect to host audit page

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

How reproducible: Always

Steps to Reproduce:
1. visit All Hosts -> click on any host
2. Click on Audits link on left side Host details section
3. Render json result

Actual results: Json result

Expected results: Should go to host audit page

Additional info:

Comment 5 Ondřej Pražák 2020-03-02 09:37:50 UTC
Created redmine issue https://projects.theforeman.org/issues/29230 from this bug

Comment 6 Bryan Kearney 2020-03-02 15:05:15 UTC
Upstream bug assigned to oprazak

Comment 7 Bryan Kearney 2020-03-02 15:05:16 UTC
Upstream bug assigned to oprazak

Comment 8 Bryan Kearney 2020-03-04 13:04:50 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29230 has been resolved.

Comment 10 Roman Plevka 2020-03-09 16:22:21 UTC
on sat6.7.0 snap #15

- the Audits button now correctly leads to the audits page with an appropriate filter applied: "host = <host name>"

Comment 13 errata-xmlrpc 2020-04-14 13:28:54 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.