Bug 815780 - Corosync systemd unit file should start corosync after network is started
Summary: Corosync systemd unit file should start corosync after network is started
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Massimo Di Nitto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-24 13:47 UTC by Jan Friesse
Modified: 2012-05-21 12:56 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-21 12:56:32 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan Friesse 2012-04-24 13:47:26 UTC 
Description of problem:
SSIA

Version-Release number of selected component (if applicable):
Upstream master

How reproducible:
As systemd god decides.

  
Actual results:
Corosync can be started before network is up.

Expected results:
Corosync starts after network is up.

Additional info:
Assigning directly to Angys, because he was working on unitfile.
Comment 1 Milan Broz 2012-04-24 16:34:46 UTC 
IMHO adding 
After=network.target
Requires=network.target

should help...
Comment 2 Fabio Massimo Di Nitto 2012-05-21 12:56:32 UTC 
now fixed upstream
Note You need to log in before you can comment on or make changes to this bug.