Bug 1825233 - Neutron kill-scripts shouldn't be used for processes which aren't run in sidecar containers
Summary: Neutron kill-scripts shouldn't be used for processes which aren't run in side...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Brent Eagles
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks: 1824397
TreeView+ depends on / blocked
 
Reported: 2020-04-17 12:55 UTC by Slawek Kaplonski
Modified: 2020-06-08 15:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-08 15:31:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1873460 0 None None None 2020-04-17 13:25:11 UTC
OpenStack gerrit 722170 0 None ABANDONED parameterize generation of the kill scripts 2020-11-12 01:29:50 UTC

Description Slawek Kaplonski 2020-04-17 12:55:43 UTC
After patch https://opendev.org/openstack/tripleo-heat-templates/commit/2dc7066b050ecf22dc9e5909061272ffe765ebfc there are "kill scripts" for all processes managed by e.g. L3 agent, even for radvd which isn't run in sidecar container but in neutron-l3-agent container directly.
That is causing various issues. First one was in Neutron, and is covered by BZ1823795.
But with fix for BZ1823795 we hit another issue. As radvd-kill script is now allowed to be executed by neutron-l3-agent, it finds neutron-l3-agent container and kills it.
So every time when radvd is killed by neutron-l3-agent because e.g. IPv6 subnet is deleted from router, agent is also restarted (killed by radvd-kill script and started back by systemd).

Comment 3 Bernard Cafarelli 2020-04-29 14:11:40 UTC
I linked current WIP upstream patch, though focus currently is on related bug #1827276

Comment 4 Bernard Cafarelli 2020-06-08 15:31:44 UTC
Whole system was reverted for 16.1, so this bug is no longer relevant, closing


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