Reviewed: https://review.openstack.org/362828 Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=6c9eb50fd64cb791a73ef778315f9a52b8c434c8 Submitter: Jenkins Branch: liberty commit 6c9eb50fd64cb791a73ef778315f9a52b8c434c8 Author: Major Hayden <major at mhtx.net> Date: Mon Aug 29 11:11:09 2016 -0500 Ensure AIDE initializes on subsequent runs If a deployer installs AIDE the first time they apply the role without initializing AIDE and they want to initialize it later, the handler that does the initialization never fires. This patch does a few things: - Ensures AIDE initialization if the initialize_aide bool is True - Doesn't intialize the AIDE db if it already exists - Moves the new db into place on Red Hat systems - Moves the AIDE tasks into its own file with tags - Prevents AIDE from trawling through /var Manual backport of two reviews: * https://review.openstack.org/#/c/359554/ * https://review.openstack.org/#/c/361460/ Closes-Bug: 1616281 Backport-of: I170eb3898b4336333b1fbe663ec4f069823898e0 Change-Id: Iaedcce1d6416f2224f44376336c23702e6152a00 ** Tags added: in-liberty -- You received this bug notification because you are a member of OpenStack Security, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1616281 Title: Can't initialize AIDE during subsequent playbook runs Status in openstack-ansible: Fix Released Bug description: AIDE isn't initialized by default because it can cause a lot of system load when it does its first check of a new system. If a deployer applies the security hardening role with ``initialize_aide`` set to False (the default), it won't be initialized. However, if they set it to True and re-run the playbook, AIDE is already configured and the handler to initialize AIDE won't execute. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1616281/+subscriptions