Description of problem: After the fix for bz#818754, it's possible that a device with ONBOOT=yes initializes openvswitch-nonetwork which starts the daemons, but openvswitch service is left stopped. Version-Release number of selected component (if applicable): openvswitch-1.10.0-6.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure an OVS interface with ONBOOT=yes 2. Disable NM, enable network script 3. Reboot Actual results: The openvswitch service is stopped but the daemons started by openvswitch-nonetwork are running. Expected results: The openvswitch service should reflect the actual situation. The following patch fixes the issue by changing -nonetwork service to start openvswitch service using 'Wants='. --- /usr/lib/systemd/system/openvswitch-nonetwork.service 2013-08-13 15:59:37.065366471 -0300 +++ /usr/lib/systemd/system/openvswitch-nonetwork.service 2013-08-13 22:37:35.561131489 -0300 @@ -2,6 +2,7 @@ Description=Open vSwitch Internal Unit After=syslog.target PartOf=openvswitch.service +Wants=openvswitch.service [Service] Type=oneshot
openvswitch-1.10.0-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/openvswitch-1.10.0-7.fc19
openvswitch-1.10.0-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20