Problem: Playbooks with vars_prompt are waiting for input

[basskitty]

Issue

I have a few playbooks with vars_prompt variables. In the Semaphore tasks these are configured as Survey Variables and most of them are optional (as there are default values configured).

These tasks stopped working a few weeks ago as they are waiting for input on the optional fields.
Earlier, there was this line in the task logs, and it worked as desired:

[WARNING]: Not prompting as we are not in interactive mode

But now this warning doesn't appear anymore and the task hangs on "Running" forever right after loading the inventory.

1:12:59 PM
Parsed /etc/ansible/hosts inventory source with yaml plugin
1:12:59 PM
Loading collection community.general from /usr/local/lib/python3.9/dist-packages/ansible_collections/community/general

Once I force Stop the task, I can see that Ansible waited for input for a variable (Sudo permissions):

1:12:59 PM
Parsed /etc/ansible/hosts inventory source with yaml plugin
1:12:59 PM
Loading collection community.general from /usr/local/lib/python3.9/dist-packages/ansible_collections/community/general
1:16:55 PM
Sudo permissions (true/false) [False]:
1:16:55 PM
Running app failed: signal: killed

It took me a while to figure out what is actually happening, so I don't know when this issue started. I did try to rollback to the Semaphore version where it last worked (v2.9.112) but this didn't resolve it, so I'm completely lost here.

Impact

Ansible (task execution)

Installation method

Package

Database

MySQL

Browser

No response

Semaphore Version

2.10.22-e44910d-1721658299

Ansible Version

ansible [core 2.15.12]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /root/.local/lib/python3.9/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] (/usr/bin/python3)
  jinja version = 3.1.2
  libyaml = True

Logs & errors

No response

Manual installation - system information

Linux ansible 5.10.0-30-amd64 #1 SMP Debian 5.10.218-1 (2024-06-01) x86_64 GNU/Linux

Configuration

No response

Additional information

No response

[setola]

Hello, I've encountered the same issue.

I've temporary bypassed it by moving vars_prompt section to a new playbook with the same name of the original and "_manual" suffix.

Then I've added the same variables in the semaphore gui.

99% of the time I run <playbook_name>.yaml from the GUI, when I need to run it on the command line I use the <playbook_name>_manual.yaml.

It's really dirty and ugly but works in my use-case... without too much code duplication.

[mathijs-dumon]

I can +1 this - I upgraded from 2.9.37 to 2.15.0 and now face this problem

[fiftin]

@mathijs-dumon Could you provide more details.