Bug 1443992 - Restarting openvswitch triggers neutron-openvswitch-agent to start
Summary: Restarting openvswitch triggers neutron-openvswitch-agent to start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On: 1436021
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-20 11:51 UTC by Jaroslav Reznik
Modified: 2017-05-25 15:52 UTC (History)
18 users (show)

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.
Clone Of: 1436021
Environment:
Last Closed: 2017-05-25 15:52:30 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1311 normal SHIPPED_LIVE systemd bug fix update 2017-05-25 19:33:32 UTC
RDO 5951 None None None 2017-04-20 11:52:03 UTC
Launchpad 1671504 None None None 2017-04-20 11:52:03 UTC

Description Jaroslav Reznik 2017-04-20 11:51:50 UTC
This bug has been copied from bug #1436021 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 6 errata-xmlrpc 2017-05-25 15:52:30 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


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