Ansible prepare step of imported plan does not work #2935
Comments
|
I found out, that commenting out |
mkluson
added a commit
to mkluson/tmt
that referenced
this issue
Jun 5, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` tries to guess absolute path to the first one. For imported plan such path does not exists. When `_ansible_playbook_path` is not called the second copy of the ansible playbook (and other files from worktree) is used and the prep step works imported plans too. Resolves: teemtee#2935
mkluson
added a commit
to mkluson/tmt
that referenced
this issue
Jun 19, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` uses the second one instead the first one now. Resolves: teemtee#2935
psss
pushed a commit
to mkluson/tmt
that referenced
this issue
Jun 25, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` uses the second one instead the first one now. Resolves: teemtee#2935
happz
pushed a commit
to mkluson/tmt
that referenced
this issue
Jun 25, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` uses the second one instead the first one now. Resolves: teemtee#2935
happz
pushed a commit
to mkluson/tmt
that referenced
this issue
Jun 26, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` uses the second one instead the first one now. Resolves: teemtee#2935
happz
pushed a commit
that referenced
this issue
Jun 26, 2024
During `tmt run` execution there are two copies of the playbook available: - One in the original repository with tmt plan - Second in the `worktree` under /var/tmp/tmt... `_ansible_playbook_path` uses the second one instead the first one now. Resolves: #2935
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use import plan feature [1] and the imported plan has one of prepare steps implemented via Ansible, the execution fails, because it can not find the playbook. E.g.:
ERROR! the playbook: /var/ARTIFACTS/git-masternbv9uido/ansible/setup_to_run_leapp.yml could not be found[1] https://tmt.readthedocs.io/en/stable/spec/plans.html#import-plans
The text was updated successfully, but these errors were encountered: