debconf: MODULE FAILURE (not enough values to unpack (expected 4, got 3))

[ArmandasRokas]

Summary

After the update from core 2.15 to core 2.16 debconf suddenly breaks running the task multiple times.

Issue Type

Bug Report

Component Name

debconf

Ansible Version

ansible [core 2.16.5]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/ansible/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  ansible collection location = /home/ansible/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.0.3
  libyaml = True

Configuration

[defaults]
roles_path=./XXXXXX/roles
collections_path=./XXXXXX
remote_user=XXXXXX
vault_password_file=~/.XXXXXX
timeout=60

OS / Environment

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

Steps to Reproduce

- name: Debconf for phpmyadmin/mysql/app-pass
  ansible.builtin.debconf:
    name: phpmyadmin
    question: phpmyadmin/mysql/app-pass
    value: "{{ php_mysql_application_password_for_phpmyadmin }}"
    vtype: password

Expected Results

I expect debconf updated with the given password.

Actual Results

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ValueError: not enough values to unpack (expected 4, got 3)
fatal: [partner-site-dev]: FAILED! => {"changed": false, "module_stderr": "Shared connection to 172.18.165.198 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n  File \"/home/ubuntu/.ansible/tmp/ansible-tmp-1715170809.149087-85672-153389685417787/AnsiballZ_debconf.py\", line 107, in <module>\r\n    _ansiballz_main()\r\n  File \"/home/ubuntu/.ansible/tmp/ansible-tmp-1715170809.149087-85672-153389685417787/AnsiballZ_debconf.py\", line 99, in _ansiballz_main\r\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n  File \"/home/ubuntu/.ansible/tmp/ansible-tmp-1715170809.149087-85672-153389685417787/AnsiballZ_debconf.py\", line 47, in invoke_module\r\n    runpy.run_module(mod_name='ansible.modules.debconf', init_globals=dict(_module_fqn='ansible.modules.debconf', _modlib_path=modlib_path),\r\n  File \"<frozen runpy>\", line 226, in run_module\r\n  File \"<frozen runpy>\", line 98, in _run_module_code\r\n  File \"<frozen runpy>\", line 88, in _run_code\r\n  File \"/tmp/ansible_ansible.builtin.debconf_payload_73rof192/ansible_ansible.builtin.debconf_payload.zip/ansible/modules/debconf.py\", line 252, in <module>\r\n    \r\n  File \"/tmp/ansible_ansible.builtin.debconf_payload_73rof192/ansible_ansible.builtin.debconf_payload.zip/ansible/modules/debconf.py\", line 223, in main\r\n    self.dccomm.wait()\r\n
    ^^^^\r\n  File \"/tmp/ansible_ansible.builtin.debconf_payload_73rof192/ansible_ansible.builtin.debconf_payload.zip/ansible/modules/debconf.py\", line 147, in get_password_value\r\n    else:\r\n^^^^^^^^^^\r\nValueError: not enough values to unpack (expected 4, got 3)\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibot]

Files identified in the description:

• lib/ansible/modules/debconf.py

If these files are incorrect, please update the component name section of the description or use the component bot command.

[Akasurde]

@ArmandasRokas Could you please check if PR #83217 works for you and let me know? Thanks in advance.

[ArmandasRokas]

@ArmandasRokas Could you please check if PR #83217 works for you and let me know? Thanks in advance.

Seems to be working right now.

TASK [XXXXXX : Debconf for phpmyadmin/mysql/app-pass] *****************************************************
--- before
+++ after
@@ -1,3 +1,3 @@
 {
-    "phpmyadmin/mysql/app-pass": "(password omitted)"
+    "phpmyadmin/mysql/app-pass": "XXXXXX"
 }

changed: [XXXXX]

However it shows still "changed" although the given password was the same as in the previous run.
So it does not look like this idempotency is working:
#81484

[Akasurde]

@ArmandasRokas Can you please check the updated patch and let me know if it works for you? Thanks.

[fermosan]

@Akasurde Hello, i had the same issue and i can confirm that your patch fixes the issue.