adoptium / adoptium/infrastructure
EPEL install on EL8+ needs to be modified
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
At the moment the playbooks will not run on an EL8+ system unless the EPEL packages are already installed. The playbooks try to install the `epel-release` package in the repositories but that does not exist on the EL distributions so it needs to be installed via an explicit RPM link as mentioned in https://github.com/adoptium/infrastructure/issues/3914#issuecomment-3468269957. We should make changes to the playbooks in order to support automatically installing EPEL from an RPM in this way.
`169.63.185.12` is a system accessible to the infrastructure team for analysis.
Contributor guide
Research direction
Read the playbooks that install EPEL and the referenced infrastructure issue comment for the EL8+ RPM approach. Use the available EL8+ system at 169.63.185.12 for analysis if appropriate, then verify that a clean EL8+ host can run the playbooks without preinstalled EPEL packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100