[openstack-ansible][wallaby] lxc-containers-create.yml fails when specifying a container group
Hello everyone, Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option. For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} Any similar experience ? Any idea ? Thank you, Jean-Francois
Hey, You should always include "lxc_hosts" to the limit when running lxc-containers-create.yml чт, 18 авг. 2022 г., 11:05 Taltavull Jean-François < jean-francois.taltavull@elca.ch>:
Hello everyone,
Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option.
For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container
Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"}
Any similar experience ? Any idea ?
Thank you, Jean-Francois
Thanks a lot Dmitriy, it works with -l “repo_container,lxc_hosts” ! Jean-Francois From: Dmitriy Rabotyagov <noonedeadpunk@gmail.com> Sent: jeudi, 18 août 2022 11:13 To: Taltavull Jean-François <jean-francois.taltavull@elca.ch> Cc: openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [openstack-ansible][wallaby] lxc-containers-create.yml fails when specifying a container group EXTERNAL MESSAGE - This email comes from outside ELCA companies. Hey, You should always include "lxc_hosts" to the limit when running lxc-containers-create.yml чт, 18 авг. 2022 г., 11:05 Taltavull Jean-François <jean-francois.taltavull@elca.ch<mailto:jean-francois.taltavull@elca.ch>>: Hello everyone, Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option. For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} Any similar experience ? Any idea ? Thank you, Jean-Francois
participants (2)
-
Dmitriy Rabotyagov
-
Taltavull Jean-François