adoptium / adoptium/infrastructure

Ansible request for boot JDK installation checks

Open
#2,624 1 comment 0 reactions 0 assignees View on GitHub
ansible good first issue
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

Please put the name of the software product (and affected platforms if relevant) in the title of this issue

Delete as appropriate from this list:

- Bug in ansible playbook

Details:
If the machine has a directory /usr/lib/jvm/jdk-17.* but no corresponding symlink from `/usr/lib/jvm/jdk-17` then the adoptopenjdk-install role will go into the "Does not exist - install it" mode and install the latest version, and if that's not the same as the one that was on the machine it will get confused by the presence of two candidate directories for the symlink target, and therefore not create one and abort the playbook.

Contributor guide

Open the contributing guide

Research direction

Locate the adoptopenjdk-install role and inspect the checks for /usr/lib/jvm/jdk-17.* directories and the /usr/lib/jvm/jdk-17 symlink. Reproduce the case with an existing versioned directory but no symlink, then verify that the playbook selects the existing installation and completes without conflicting candidates.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.