Bug #23913
closedhost global_status changes should not be audited
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1590328
Description of problem:
the "last_checkin" and "global_status" attr. changes shouldn't be audited. This is currently audited and generates a lot of audit records.
Version-Release number of selected component (if applicable):
6.4.0-7
Steps to Reproduce:
1. register a content host to a satellite
2. check audits for a host-related record showing the global_status change
3. now edit the update interval parameter in /etc/rhsm/rhsm.conf on the host to 1 minute and check the audit page for the host->last checkin records
Actual results:
the above attr changes are audited
Expected results:
the above attr changes are excluded from auditing
Updated by Tomer Brisker over 6 years ago
- Copied to Bug #23914: host last_checkin changes should not be audited added
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Tomer Brisker
- Pull request https://github.com/theforeman/foreman/pull/5686 added
Updated by Timo Goebel over 6 years ago
- Subject changed from host global_status changes should not be audited to host global_status changes should not be audited
- Translation missing: en.field_release set to 353
Updated by Tomer Brisker over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 9e1851e474bcd9351c445577438e1ad8982b5ab0.
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/foreman/pull/5717 added
Updated by Ondřej Pražák over 6 years ago
- Translation missing: en.field_release changed from 353 to 330