Bug 1825233

Summary: Neutron kill-scripts shouldn't be used for processes which aren't run in sidecar containers
Product: Red Hat OpenStack Reporter: Slawek Kaplonski <skaplons>
Component: openstack-tripleo-heat-templatesAssignee: Brent Eagles <beagles>
Status: CLOSED CURRENTRELEASE QA Contact: David Rosenfeld <drosenfe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 16.0 (Train)CC: amuller, bcafarel, bdobreli, mburns, mkrcmari
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-08 15:31:44 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: 1824397    

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