openstack-ansible-security needs a check mode for auditing

Bug #1516142 reported by Major Hayden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Wishlist
Major Hayden

Bug Description

The openstack-ansible-security role should be fully functional in Ansible's check mode and it should provide output that is beneficial for auditing existing environments or providing some reporting on what will be changed when the role is run without check mode.

Changed in openstack-ansible:
assignee: nobody → Major Hayden (rackerhacker)
Changed in openstack-ansible:
importance: Undecided → Wishlist
status: New → Triaged
milestone: none → 12.1.0
Changed in openstack-ansible:
status: Triaged → In Progress
Revision history for this message
Major Hayden (rackerhacker) wrote :
Changed in openstack-ansible:
milestone: 12.1.0 → mitaka-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-security (master)

Reviewed: https://review.openstack.org/245813
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=3e2e66db6375bf05dcbd81fc8273ee9e26e46073
Submitter: Jenkins
Branch: master

commit 3e2e66db6375bf05dcbd81fc8273ee9e26e46073
Author: Major Hayden <email address hidden>
Date: Tue Dec 1 08:24:17 2015 -0600

    Check mode compatibility for security role

    Closes-bug: 1516142

    Implements: blueprint security-hardening

    Change-Id: Ia38fbdd8bd8fa5aaef1252569563bf0a829f095d

Changed in openstack-ansible:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.