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

RHEL package update overwrites systemd config file

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • packaging
    • RHEL8 system - Jenkins Update from 2.387 (LTS) to 2.414 (LTS) via dnf (pkg.jenkins.io/redhat-stable/jenkins.repo)

      When updating Jenkins via yum/dnf, the package overwrites the systemd config file located under /usr/lib/systemd/system/jenkins.service. Configurations (i.e. HTTPS-Setup) will be overwritten on every update. A standard package update procedure on RHEL is not intended to update configuration files such as the systemd service file, unless there are neccessary changes in said files.

      To stop this behaviour, including a diff-check on these files would be great.

          [JENKINS-71910] RHEL package update overwrites systemd config file

          Mark Waite added a comment - - edited

          Administrators should use the override mechanism provided by systemd rather than modifying system provided files directly. The Jenkins documentation includes instructions in "Managing systemd services" that describe the technique for all supported Linux distributions using systemd.

          The Red Hat Enterprise Linux 8 documentation says:

          Services installed on the system come with default unit files that are stored in the /usr/lib/systemd/system/ directory. System Administrators should not modify these files directly, therefore any customization must be confined to configuration files in the /etc/systemd/system/ directory.

          Mark Waite added a comment - - edited Administrators should use the override mechanism provided by systemd rather than modifying system provided files directly. The Jenkins documentation includes instructions in "Managing systemd services" that describe the technique for all supported Linux distributions using systemd. The Red Hat Enterprise Linux 8 documentation says: Services installed on the system come with default unit files that are stored in the /usr/lib/systemd/system/ directory. System Administrators should not modify these files directly , therefore any customization must be confined to configuration files in the /etc/systemd/system/ directory.

            Unassigned Unassigned
            ger_senshi Julian Krieger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: