Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1692475 - Audit page shows "auditable id / Lifecycle environment" for "HOST" when changing Content View and Lifecycle Environment
Summary: Audit page shows "auditable id / Lifecycle environment" for "HOST" when chang...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Audit Log
Version: 6.5.0
Hardware: All
OS: Linux
unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-25 16:49 UTC by Dylan Gross
Modified: 2019-03-26 17:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Dylan Gross 2019-03-25 16:49:59 UTC
Description of problem:

If you go into a Content Host and change it's Lifecycle Environment and Content View, and then view the "Monitor"->"Audits", the audit entry does not list the host that was just modified.  It lists the auditable id number and the Lifecycle Environment. 


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

    Red Hat Satellite 6.5 Beta

How reproducible:


Steps to Reproduce:
1.   Change the Lifecycle Environment and Content View of a Content Host
2.   Navigate to "Monitor" and then "Audits"

Actual results:
 
  The resulting event will be something like:

     Admin (IP)    updated        HOST    44 / Dev

  Expanding the audit event also does not show the hostname


Expected results:

  It would be useful and somewhat intuitive if the hostname for the Content Host change was reflected in the audit event.
Additional info:


Note You need to log in before you can comment on or make changes to this bug.