• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: packaging
• Labels:

  None
• Environment:

  CentOS 7, CentOS 8, Amazon Linux 2, Oracle Linux 7, Oracle Linux 8, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Scientific Linux 7, Alma Linux 8

[JENKINS-66359] 2.306 RPM installer fails unless epel repository is enabled

Mark Waite created issue - 2021-08-11 16:30

Mark Waite made changes - 2021-08-11 19:34

Remote Link

New: This issue links to "PR-4506 add epel-release to CentOS install instructions (Web Link)" [ 26857 ]

Mark Waite made changes - 2021-08-11 19:40

Assignee

New: Mark Waite [ markewaite ]

Mark Waite made changes - 2021-08-11 19:41

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Mark Waite made changes - 2021-08-12 12:22

Description

Original: The Jenkins 2.306 rpm packaging requires the `daemonize` package so that it can remove some outdated Java code and be consistent with the Debian package. Unfortunately, the `daemonize` package is available from the `epel` repository and that repository is not enabled by default. A little embarassing for me, since one of the items on the weekly and LTS release checklist is to confirm that https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-latest-redhat-rpm/ is passing. It started failing with the release of Jenkins 2.306 because the test configuration does not include the `epel` repository. I ran through the checklist yesterday, but skipped the check of the rpm installer while verifying Docker image tags. I didn't go back to check again. Should we update the installation documentation to enable the epel repository or is there another approach we should consider?

New: The Jenkins 2.306 rpm packaging requires the `daemonize` package so that it can remove some outdated Java code and be consistent with the Debian package. Unfortunately, the `daemonize` package is available from the `epel` repository and that repository is not enabled by default. A little embarassing for me, since one of the items on the weekly and LTS release checklist is to confirm that https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-latest-redhat-rpm/ is passing. It started failing with the release of Jenkins 2.306 because the test configuration does not include the `epel` repository. I ran through the checklist yesterday, but skipped the check of the rpm installer while verifying Docker image tags. I didn't go back to check again. Should we update the installation documentation to enable the epel repository or is there another approach we should consider? Installation documentation on www.jenkins.io has been updated. Installation instructions on https://pkg.jenkins.io/redhat/ have not been updated and are now even more out of date with the documentation on www.jenkins.io.

Mark Waite made changes - 2021-08-12 18:06

Remote Link

New: This issue links to "PR-210 for https://pkg.jenkins.io/redhat and https://pkg.jenkins.io/redhat-stable (Web Link)" [ 26858 ]

Mark Waite made changes - 2021-08-12 18:07

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Collapse comment: Mark Waite added a comment - 2021-08-12 19:32

Mark Waite added a comment - 2021-08-12 19:32

Pull requests are merged and instructions should be changed the next time the site is updated (Jenkins 2.307?)

Expand comment: Mark Waite added a comment - 2021-08-12 19:32

Mark Waite added a comment - 2021-08-12 19:32 Pull requests are merged and instructions should be changed the next time the site is updated (Jenkins 2.307?)

Mark Waite made changes - 2021-08-12 19:32

Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2021-08-12 19:32

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Load more newer events