4496600249
[1] has been merged and released[2] in upstream tox-ansible and it is now able to manage global molecule configuration. The workaround, which consisted in adding the molecule driver name in each scenarios molecule.yml files, is not necessary anymore. This patch also removes all the relative symlink to the Dockerfile and adds directly in the global molecule configuration file. [1] https://github.com/ansible-community/tox-ansible/pull/89 [2] https://github.com/ansible-community/tox-ansible/releases/tag/v1.5.0 Signed-off-by: Gael Chamoulaud (Strider) <gchamoul@redhat.com> Change-Id: I259c17b7a49ff5bf3476df4da399cc4b2782403d (cherry picked from commitc551910cf5) (cherry picked from commitf3cba823d7)
Undercloud-tokenflush
An Ansible role to check if keystone-manage token_flush is enabled for the keystone user.
Requirements
This role requires an installed and working Undercloud.
Role Variables
- cron_check: <'keystone-manage token_flush'> -- the string to check in the crontab
Dependencies
No dependencies.
Example Playbook
- hosts: undercloud
roles:
- { role: undercloud-tokenflush }
License
Apache
Author Information
Red Hat TripleO Validations Team