Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1869417

Summary: /usr/lib/systemd/system/munge.service:10: PIDFile= references a path below legacy directory /var/run/
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: mungeAssignee: Ankur Sinha (FranciscoD) <sanjay.ankur>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: cdunlap, gp, neuro-sig, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: munge-0.5.14-4.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-09 01:34:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Orion Poplawski 2020-08-17 22:57:18 UTC
Description of problem:

/usr/lib/systemd/system/munge.service:10: PIDFile= references a path below legacy directory /var/run/, updating /var/run/munge/munged.pid → /run/munge/munged.pid; please update the unit file accordingly.

Version-Release number of selected component (if applicable):
munge-0.5.13-5.fc31.x86_64

Comment 1 Ben Cotton 2020-11-03 17:16:45 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Orion Poplawski 2020-11-03 22:24:19 UTC
Still present in 0.5.13-7.fc32.  Looks like munge's configure accepts a --runstatedir=DIR option which could get set to /run.  You would also want to change the location of the .pid file in your spec (touch/%files).

Comment 3 Ankur Sinha (FranciscoD) 2020-11-04 09:47:21 UTC
Thanks Orion, on my task list now. Will hopefully get to it this week or the next.

Comment 4 Chris Dunlap 2020-11-09 21:06:26 UTC
For 0.5.13, you will also want to change PIDFile= in src/etc/munge.service.in accordingly.

0.5.14 has better support for runstatedir. You would only need to update the munge.spec %configure line to specify either "--runstatedir=%{_rundir}" (if using the distributed configure script) or "--with-runstatedir=%{_rundir}" (if running autoreconf).

Comment 5 Ankur Sinha (FranciscoD) 2020-11-17 22:49:22 UTC
I've updated to 0.5.14 and made the necessary updates to the spec.

Chris, Orion, would you please be able to take a quick peek before I build and push updates? I don't have a setup to be able to test it out myself.
I've opened a PR here:

https://src.fedoraproject.org/rpms/munge/pull-request/2

Thanks very much,
Ankur

Comment 6 Chris Dunlap 2020-11-18 05:01:55 UTC
I added a few comments in the pull request.

Comment 7 Fedora Program Management 2021-04-29 17:11:06 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora Update System 2021-04-30 08:59:55 UTC
FEDORA-2021-769378b3af has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-769378b3af

Comment 9 Fedora Update System 2021-05-01 02:05:05 UTC
FEDORA-2021-769378b3af has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-769378b3af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-769378b3af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2021-05-09 01:34:12 UTC
FEDORA-2021-769378b3af has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.