Bug 1417243
Summary: | some ovs systemd services remain inactive when an individual service has been stopped and then started | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Rick Alongi <ralongi> |
Component: | openvswitch | Assignee: | Eelco Chaudron <echaudro> |
Status: | CLOSED NOTABUG | QA Contact: | ovs-qe |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | aconole, atragler, echaudro |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-07 10:48:17 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
Rick Alongi
2017-01-27 16:31:40 UTC
some of this is intended (as the ovsdb service needs be started/stopped independently in case bad values are pushed into the database that causes the whole thing to tear down). Regardless, I agree we should go through and make sure all the states are consistent. Looking at your tests and the dependencies this is working per design. You should start/stop openvswitch using the openvswitch service, not stopping and starting the sub-services. Let me explain; openvswitch has a dependency on both ovs-vswtichd or ovsdb-server. So if one of those gets stopped openvswitch also gets stopped (including dependant services). So this is why if any of the two gets stopped all 3 services are stopped. Now if you try to control individual services they will not trigger openvswitch to be up, but only themselves. ovs-vswitchd also depends on ovsdb-server and that's why this one is also brought up in the ovs-vswitchd case. Hope this clears thinks up. If not please, let me know. |