Change abandoned by Major Hayden (major at mhtx.net) on branch: stable/mitaka Review: https://review.openstack.org/323536 Reason: Most of the Ansible 2.x users will be using the master (Newton) branch of the security role anyway. -- 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