Debian 12 wildfly_systemd issue

[eric-maletras]

SUMMARY

Installation failed on wildfly install system d.
I think is on file 'wildfly_systemd/tasks/systemd.yml' lines 116-123

ISSUE TYPE

cmd": "set -o pipefail \nupdate-alternatives --query java | grep 'Value: ' | grep -o '/.*/jre'\n"
"msg": "non-zero return code", "rc": 1,

ANSIBLE VERSION

ansible [core 2.14.3]
  config file = None
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] (/usr/bin/python3)
  jinja version = 3.1.2
  libyaml = True

COLLECTION VERSION

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

[TheUsefulNerd]

Hi,
I am new to open-source contributions. Can you explain this problem in more detail?

[rpelisse]

@TheUsefulNerd I think this particular issue is specific to Debian. As pointed out by @eric-maletras , the command line executed by Ansible in the playbook wildfly_systemd/tasks/systemd.yml is not working on Debian simply because the JDK is not installed in the same place.
To walk you through what needs to be done: copy one of the existing molecule scenario (default) an change the target system to Debian. Run the molecule scenario : it should failed because of the issue pointed out by @eric-maletras . Then you can externalise (into a variable) the path to the JDK home and use some logic to select this path based on the ansible_os_family value (so the current value for RedHat family or the one for Debian for the Debian family).
I hope this helps!