Bug 984847 - munged.service should start after network.target
munged.service should start after network.target
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: munge (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Steve Traylen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-16 03:43 EDT by Yu Watanabe
Modified: 2013-08-30 11:19 EDT (History)
1 user (show)

See Also:
Fixed In Version: munge-0.5.11-1.fc20
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-30 11:19:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yu Watanabe 2013-07-16 03:43:34 EDT
Description of problem:

Munged always fail to start on the system boot with:
  munged: Error: Unable to resolve host ....


Version-Release number of selected component (if applicable):
munge-0.5.10-4.fc18.x86_64
munge-0.5.10-5.fc19.x86_64

How reproducible:

Always the system booting

Steps to Reproduce:
1. just reboot the system
2.
3.

Actual results:

  munged: Error: Unable to resolve host ....

Expected results:

Munged should be correctly start

Additional info:

This bug is already reported at
https://code.google.com/p/munge/issues/detail?id=11
and the workaround for this problem is 
create /etc/systemd/system/munged.service.d/after-network.conf as

[Unit]
After=network.target

This bug is also exist on fedora 18.

Note You need to log in before you can comment on or make changes to this bug.