Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Linux, CentOS and Fedora. Using RPM installation and upgrade
Description
I have a Jenkins installation for which I changed the "JENKINS_USER" and "JENKINS_HOME" (in /etc/sysconfig/jenkins) from the defaults.
When I do an upgrade via yum/RPM, it sets the ownership of /var/log/jenkins back to default user "jenkins" (instead of honoring my JENKINS_USER configuration).
This prevents Jenkins from starting after an upgrade. And since it cannot write to the log file, it may not be easy to figure out what went wrong.
Attachments
Issue Links
- is related to
-
JENKINS-23273 RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
-
- Resolved
-
Is there a reason the patch does not include /var/cache/jenkins? And that it's recursive is probably really unnecessary, as noted in
JENKINS-23273.Francisco Lozano: Doesn't your /etc/sysconfig/jenkins define as JENKINS_USER the name of the Jenkins user?