Reviewed: https://review.openstack.org/320637 Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=9fbe88ab28cf6b546325d4821e543e73b1a04324 Submitter: Jenkins Branch: master commit 9fbe88ab28cf6b546325d4821e543e73b1a04324 Author: Major Hayden <major at mhtx.net> Date: Tue May 24 14:53:59 2016 -0500 Fix unlocked account check on Ansible 2.2 The unlocked account check for V-34896 always fails in Ansible 2.2, even when there are no unlocked accounts on the system. This patch simplifies the jinja loop and rejects any empty lines. Closes-bug: 1585349 Change-Id: I11728e24f341ec696da3a761f02087266341cf2a ** Changed in: openstack-ansible Status: In Progress => Fix Released -- You received this bug notification because you are a member of OpenStack Security, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1585349 Title: Security role fails on unlocked accounts in Ansible 2.2 Status in openstack-ansible: Fix Released Bug description: The security role fails on the unlocked accounts check when using Ansible 2.2: TASK [openstack-ansible-security : debug] ************************************** ok: [logs.cloud-ci.ibmcis.com] => { "v38496_violations": "\n" } The tasks end up returning a non-empty violations list even though no unlocked accounts exist on the system. Thanks to phschwartz for reporting this in IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1585349/+subscriptions