Reviewed: https://review.openstack.org/328285 Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=cc45bade6a63472a704deb2093c845f5541d895b Submitter: Jenkins Branch: stable/mitaka commit cc45bade6a63472a704deb2093c845f5541d895b Author: Major Hayden <major at mhtx.net> Date: Thu Jun 9 13:42:18 2016 -0500 Add key fields to audit rules This patch adjusts the key fields in the audit rules that are added by the security rule to make it easier to link a log entry with the audit rules that caused it. Deployers with overflowing logs should be able to narrow down the rule much more easily. A manual cherry-pick of I39c673d515467f685004463e914a0a1aaec3c153 is required since the master branch has some additions for SELinux that don't make sense in Mitaka or Liberty. Closes-Bug: 1590911 Change-Id: I5c8757333eb22f35a120d78c8772f53c1c0bb9ca -- You received this bug notification because you are a member of OpenStack Security, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1590911 Title: Security role audit rules should have key fields Status in openstack-ansible: Fix Released Bug description: The audit rules added by the security role should have a key field added so that it's easier to figure out which rule caused something to be audited. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1590911/+subscriptions