You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to support running an ansible playbook as a test. Here's a real-life example of a reboot test from the selinux repository. The best approach would be probably to add a new framework type ansible which would allow executing the playbook and check for its exit status.
Example test metadata could look like this:
test: path/to/the/playbook.yamlframework: ansible
The text was updated successfully, but these errors were encountered:
No, it’s possible to explicitly request in playbook to execute stuff on the control node
So arbitrary commands could be executed on the tmt runner
What about ansible galaxy dependencies?
Extra packages would have to be installed on the runner
And the collection needs to be installed as well on the test runner
What about using the multihost provision instead?
One of the guests could be used as the ansible control node
tmt could provide an inventory file so that it’s easy to execute the ansible-playbook
Ideally including the ssh keys and all the stuff so that the test does not have to care about this
Using multiple guests seems to be the best approach, we need to clarify though what the exact scope of this should be, what exact should be the responsiblity of tmt and what should be left on the test.
It would be nice to support running an ansible playbook as a test. Here's a real-life example of a reboot test from the selinux repository. The best approach would be probably to add a new
framework
typeansible
which would allow executing the playbook and check for its exit status.Example test metadata could look like this:
The text was updated successfully, but these errors were encountered: