Bug 1436021

Summary:	Restarting openvswitch triggers neutron-openvswitch-agent to start
Product:	Red Hat Enterprise Linux 7	Reporter:	Tim Rozet <trozet>
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, jlibosva, jpazdziora, jreznik, jsynacek, markmc, msekleta, nyechiel, pmyers, sclewis, srevivo, systemd-maint-list
Target Milestone:	pre-dev-freeze	Keywords:	ZStream
Target Release:	7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-219-37.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1443992 (view as bug list)		Environment:
Last Closed:	2017-08-01 09:14:52 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:
Bug Depends On:
Bug Blocks:	1414325, 1443992

Description Tim Rozet 2017-03-26 20:06:10 UTC

Description of problem:
When running a tripleo deployment without neutron-openvswitch-agent enabled, if openvswitch is ever restarted, it triggers neutron-openvswitch-agent to start.

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

How reproducible:
Everytime

Steps to Reproduce:
1. Disable neutron-openvswitch-agent from compute and control profiles in tripleO:
resource_registry:
  OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None
  OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None
2. Deploy.
3. Login to a compute node
4. systemctl restart openvswitch


Actual results:
 neutron-openvswitch-agent will also start

Expected results:
 neutron-openvswitch-agent should not start

Additional info:

Comment 3 Jakub Libosvar 2017-04-11 15:45:00 UTC

This is a bug in systemd fixed in upstream. Switching component.

Comment 5 Assaf Muller 2017-04-11 16:04:32 UTC

Note that this systemd issue has been affecting OpenStack since the OSP 5 release where we started using systemd on RHEL 7. This is not a regression in OSP 11.

Comment 6 Jan Synacek 2017-04-12 06:31:59 UTC

(In reply to Jakub Libosvar from comment #3)
> This is a bug in systemd fixed in upstream.

Where?

Comment 7 Jakub Libosvar 2017-04-12 07:14:16 UTC

(In reply to Jan Synacek from comment #6)
> (In reply to Jakub Libosvar from comment #3)
> > This is a bug in systemd fixed in upstream.
> 
> Where?

Forwarding needinfo to Michal as he's the one who found the patch.

Comment 8 Michal Sekletar 2017-04-12 09:47:41 UTC

https://github.com/systemd/systemd/commit/c6497ccb7153af9a1252c48918e380b5134314de

Comment 10 Lukáš Nykrýn 2017-04-19 11:21:10 UTC

fix merged to upstream staging branch ->
https://github.com/lnykryn/systemd-rhel/commit/77f4e582d0f381391594e6f8a7b6767d572d96f7
https://github.com/lnykryn/systemd-rhel/commit/7f72b471bbfd449f4261d12cc7b062f6e7034283
-> post

Comment 19 errata-xmlrpc 2017-08-01 09:14:52 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:2297