Installation - Issue related to new Ansible version

[Olivier R]

Hi everyone,

I'm currently trying to install Dataverse 6.10.1 with Ansible, since I find it much easier and faster. It worked quite well with Dataverse 6.7.1 and Ansible 10 (Core 2.17).

I would like to report an issue with Ansible 12 (Core 2.19) which is now less permissive. The standard procedure fails if the value in a "when" clause is not a boolean. This problem occurs in the task payara.yml on line 88 and the message looks like:

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Task failed: Conditional result (False) was derived from value of type 'NoneType' at '<unknown>'. Conditionals must have a boolean result."}

This error can be bypassed by setting `ALLOW_BROKEN_CONDITIONALS`, but it would be great if the problem could be fixed in the dataverse-ansible gdcc repository. Maybe I should create an issue on GitHub.

Thanks for providing and maintaining dataverse-ansible.

Best regards,

Olivier

IPGP Datacenter

[Don Sizemore]

Thank you for reporting this. Dataverse has bundled the JDBC driver for some time now, so this is dead code that can likely be removed.

I've opened https://github.com/gdcc/dataverse-ansible/issues/432

Don

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/cf02c5cb-9a8c-4fed-bdff-3600a2ab9c31n%40googlegroups.com.

[Olivier R]

Hi Don,

I am reporting another similar issue in dataverse-install.yml, lines 90 and 99. When the value of the variable dataverse.default.config in main.yml is left blank, Ansible 12 sets the default value to null. With the previous version of Ansible, the default was set to an empty string. Therefore, a conditional test of the length of this variable no longer works and the whole procedure fails.

A solution that worked for me was to replace this test with "default_config is none" on line 90, and "default_config is not none" on line 99. However, this may not work for people using Ansible 11 or any older version. In fact, the version of Ansible to use does not seem to be specified.

I coudn't find any mention of this new behaviour in Ansible's porting guide ( https://docs.ansible.com/projects/ansible/latest/porting_guides/porting_guide_core_2.19.html ) but it is reported here : https://noobient.com/2026/03/02/ansible-changes-the-empty-string-from-string-to-nonetype/

I hope this helps to maintain dataverse-ansible updated.

Olivier