Bug 1468299 - neutron-openvswitch-agent crashes after SIGTERM is received
neutron-openvswitch-agent crashes after SIGTERM is received
Status: NEW
Product: RDO
Classification: Community
Component: openstack-neutron (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: trunk
Assigned To: Assaf Muller
Ofer Blaut
Depends On:
Blocks: 1468334
  Show dependency treegraph
Reported: 2017-07-06 11:38 EDT by David Manchado
Modified: 2017-07-26 09:39 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1468334 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Manchado 2017-07-06 11:38:38 EDT
Description of problem:
neutron-openvswitch-agent stops after receiving SIGTERM.
In the event of a sigsev on openvswitch, systemd based on to the dependencies defined send the SIGTERM signal to neutron-openvswitch-agent.
The dataplane and controlplane get disrupted.

Version-Release number of selected component (if applicable):
RDO newton
openstack-neutron.noarch        1:9.3.2-0.20170421152919.6b11276.el7.centos
python-openvswitch.noarch       1:2.6.1-4.1.git20161206.el7
openvswitch.x86_64              1:2.6.1-4.1.git20161206.el7
openstack-neutron-ml2.noarch    1:9.3.2-0.20170421152919.6b11276.el7.centos

How reproducible:

Steps to Reproduce:
1. Kill ovs-vswitchd process

Actual results:
Both openvswitch and neutron-openvswitch-agent are in inactive status

Expected results:
systemd to handle the failure and restart the services

Additional info:
This is already fixed in openvswitch 2.7 [1]

[1] https://github.com/openvswitch/ovs/commit/c19bf36d848cbdf755c6760fad1726c95e4377f1
Comment 1 Assaf Muller 2017-07-26 09:39:26 EDT
This is fixed in openvswitch-2.6.1-11.git20161206.el7ost. We need to ensure RDO Newton and Ocata (Both on OVS 2.6) should be using that version.

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