Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12231

RPM upgrade does not honor JENKINS_USER, and always resets files ownership to "jenkins"

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • 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

          Activity

            danielbeck Daniel Beck added a comment -

            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?

            danielbeck Daniel Beck added a comment - 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?
            olenz Olaf Lenz added a comment -

            I think that this issue is fixed. When setting the JENKINS_USER in /etc/sysconfig/jenkins, the ownership is set correctly. The problem about long times required to chown is handled in JENKINS-23273.

            olenz Olaf Lenz added a comment - I think that this issue is fixed. When setting the JENKINS_USER in /etc/sysconfig/jenkins, the ownership is set correctly. The problem about long times required to chown is handled in JENKINS-23273 .
            olenz Olaf Lenz added a comment -

            This is fixed since a while.

            olenz Olaf Lenz added a comment - This is fixed since a while.

            Code changed in jenkins
            User: Nicolas De loof
            Path:
            SPECS/jenkins.spec
            http://jenkins-ci.org/commit/packaging/144b7bd6ec71092162030e648c02e879506f81fa
            Log:
            [FIXED JENKINS-12231] ensure right owner
            Originally-From: jenkins-ci.org/commit/core/4335bd435f9e5258831c5631bfab2fd837fd7719

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De loof Path: SPECS/jenkins.spec http://jenkins-ci.org/commit/packaging/144b7bd6ec71092162030e648c02e879506f81fa Log: [FIXED JENKINS-12231] ensure right owner Originally-From: jenkins-ci.org/commit/core/4335bd435f9e5258831c5631bfab2fd837fd7719

            Code changed in jenkins
            User: Vojtěch-Zweibrücken-Šafařík
            Path:
            rpm/build/SPECS/jenkins.spec
            http://jenkins-ci.org/commit/packaging/d7b16bc1f25c534572ef238a885bb28571455b99
            Log:
            JENKINS-23273 Revert sticky bit to not reopen JENKINS-12231 like
            situations

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vojtěch-Zweibrücken-Šafařík Path: rpm/build/SPECS/jenkins.spec http://jenkins-ci.org/commit/packaging/d7b16bc1f25c534572ef238a885bb28571455b99 Log: JENKINS-23273 Revert sticky bit to not reopen JENKINS-12231 like situations

            People

              Unassigned Unassigned
              fernando Fernando Dobladez
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: