Juan Larriba fad1ea42ce Remove become: true from the role ... The role is always executed with --become, as it is specified in the documentation. The CLI also invokes the role with --become parameter. In this case, we were currently implementing a non consistent become policy. As almost all the tasks in the role require root access, it is more consistent to remove all the become: true entries and launch the role with --become parameter. Depends-on: Id2aff61f219b0c4992f6f0045f1aba2c7d129758 Change-Id: I263e05c905e3ea6f3f25f4e5a1b8dfb25f6a3f97		2021-06-02 07:44:53 +00:00
..
ceph_authentication.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
ceph_backup.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
ceph_mgr_stop.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
ceph_mon_stop.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
ceph_nfs_stop.yml	Use ansible_facts instead	2021-02-22 08:24:46 -07:00
ceph_rgw_stop.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
db_backup.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
main.yml	Make execution of the backup idempotent	2021-05-27 12:55:13 +02:00
pacemaker_backup.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
pacemaker_unstandby.yml	Make execution of the backup idempotent	2021-05-27 12:55:13 +02:00
run_backup.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
service_manager_pause.yml	Make execution of the backup idempotent	2021-05-27 12:55:13 +02:00
service_manager_unpause.yml	Move the snapshots feature to optional/beta	2021-05-12 10:40:08 +02:00
setup_nfs.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00
setup_rear.yml	Remove become: true from the role	2021-06-02 07:44:53 +00:00