adoptium/infrastructure

Ansible request for boot JDK installation checks

Open

#2,624 opened on Jun 21, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (104 forks)auto 404
ansiblegood first issue

Repository metrics

Stars
 (98 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Inspect the adoptopenjdk install role to locate where it checks for existing JDK installations. Identify the condition that looks for the symlink /usr/lib/jvm/jdk 17 and add logic to handle the case where a directory like /usr/lib/jvm/jdk 17.0.1 exists but no symlink is present. The fix should create the missing symlink or adjust the installation logic to avoid confusion.
Tech stack
shellpython
Domain
devops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
AnsibleLinux
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70