pg_users handling in v3.6.1

[VadimJCA]

We think there is something wrong with handling pg_users in our setup. We've deployed pigsty and a couple of PostgreSQL clusters: 17 - OK and 18 - not so OK. Grafana dashboards are alive. But when we went to add databases and users via pg_users we're got

$ ./pgsql-user.yml -l pg-almall -e username=reader

PLAY [PGSQL USER] ***************************************************************************************************************************************************************************************************************************

TASK [validate username parameter] **********************************************************************************************************************************************************************************************************
ok: [10.0.0.137] => {
    "changed": false,
    "msg": "All assertions passed"
}
ok: [10.0.0.138] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [fetch user definition] ****************************************************************************************************************************************************************************************************************
[WARNING]: an unexpected error occurred during Jinja2 environment setup: error parsing collection metadata: unhashable type: 'dict'
fatal: [10.0.0.137]: FAILED! => {"msg": "template error while templating string: error parsing collection metadata: unhashable type: 'dict'. String: {{ pg_users | json_query(user_def_query) }}"}
[WARNING]: an unexpected error occurred during Jinja2 environment setup: error parsing collection metadata: unhashable type: 'dict'
fatal: [10.0.0.138]: FAILED! => {"msg": "template error while templating string: error parsing collection metadata: unhashable type: 'dict'. String: {{ pg_users | json_query(user_def_query) }}"}

PLAY RECAP **********************************************************************************************************************************************************************************************************************************
10.0.0.137                 : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
10.0.0.138                 : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

We've tried different styles of defining pg_users, falling back to

pg_users: [{ name: reader ,password: readerS3cr3t   ,pgbouncer: true ,roles: [dbrole_readonly   ] ,comment: read-only viewer }]

for the clean test, yet still got the same error.

Is this some bootstrap package version problem?

pigsty v.3.6.1 is running under Rocky Linux 8.10, python 3.12

[Vonng]

  # check you jmespath location
  pip3 show jmespath
  python3.12 -m pip show jmespath

  # 2. which Python is used by ansible
  ansible --version

  # 3. check json_query is working
  ansible localhost -m debug -a "msg={{ [{'name': 'test'}] | json_query('[?name==`test`]') }}"`

try fix it by installing jmespath for the actual python interpreter

 python3.12 -m pip install jmespath

[VadimJCA]

Thank you so much! Ansible was using older python and the 3.12 itself wasn't installed properly. Issue is now resolved.