Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible-runner doesn't support ANSIBLE_ENABLE_TASK_DEBUGGER #1327

Closed
fao89 opened this issue Nov 21, 2023 · 3 comments
Closed

ansible-runner doesn't support ANSIBLE_ENABLE_TASK_DEBUGGER #1327

fao89 opened this issue Nov 21, 2023 · 3 comments

Comments

@fao89
Copy link

fao89 commented Nov 21, 2023

https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_debugger.html#enabling-the-debugger-in-configuration-or-an-environment-variable
When I set ANSIBLE_ENABLE_TASK_DEBUGGER=true and execute my playbook with the ansible-runner:

ansible-runner run /runner -p osp.edpm.nova

it gets stuck, and it isn't possible to use the debugger
image

If I run the same playbook with ansible-playbook

ansible-playbook -i inventory/hosts osp.edpm.nova

I can see the (debug)> prompt
image

@github-actions github-actions bot added the needs_triage New item that needs to be triaged label Nov 21, 2023
fao89 added a commit to fao89/data-plane-adoption that referenced this issue Nov 21, 2023
@sivel
Copy link
Member

sivel commented Nov 21, 2023

I'm curious why you want to have the task debugger enabled when running playbooks through runner.

@fao89
Copy link
Author

fao89 commented Nov 21, 2023

@sivel to be honest, I never used the debugger. I bumped into this issue because this var was set to true in a sample and I didn't know why my playbook was getting stuck on error. I could only see it once I ran with ansible-playbook.

bogdando pushed a commit to bogdando/data-plane-adoption that referenced this issue Nov 27, 2023
@Shrews
Copy link
Contributor

Shrews commented Nov 27, 2023

I'm going to close this because using the debugger under runner is not a scenario that is ever going to work because of the need for manual interaction with the debugger itself. Runner does not (nor will it ever) have the ability to process manual interaction with Ansible except for very limited ability to recognize and handle password prompts. If you need to use the debugger, you'll have to run ansible-playbook directly.

@Shrews Shrews closed this as completed Nov 27, 2023
@Shrews Shrews removed the needs_triage New item that needs to be triaged label Nov 27, 2023
fao89 added a commit to fao89/openstack-ansibleee-operator that referenced this issue Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants