Bug 1443992
Summary: | Restarting openvswitch triggers neutron-openvswitch-agent to start | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.3 | CC: | amuller, bblaskov, bbreard, chrisw, fsumsal, igkioka, jlibosva, jreznik, jsynacek, markmc, msekleta, nyechiel, pmyers, sclewis, srevivo, systemd-maint-list, systemd-maint, trozet |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-30.el7_3.9 | Doc Type: | Bug Fix |
Doc Text: |
Previously, if there was a require dependency between units (for example,neutron-openvswitch-agent requiring openvswitch), restarting was propagated to the dependent unit even if the dependent unit was not running. For example, restarting openvswitch started also the dependent neutron-openvswitch-agent even when it was in the stopped state. With this update, restarting propagation has been changed to try-restart, and stopped dependent units are no longer started. As a result, neutron-openvswitch-agent remains in the stopped state in the described example.
|
Story Points: | --- |
Clone Of: | 1436021 | Environment: | |
Last Closed: | 2017-05-25 15:52:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1436021 | ||
Bug Blocks: |
Description
Jaroslav Reznik
2017-04-20 11:51:50 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1311 |