Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1501750

Summary: Restarting l3 agent not spawning keepalived
Product: Red Hat OpenStack Reporter: anil venkata <vkommadi>
Component: openstack-neutronAssignee: anil venkata <vkommadi>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: amuller, apevec, bperkins, chrisw, jjoyce, nyechiel, slinaber, srevivo, vkommadi
Target Milestone: z6Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: openstack-neutron-9.4.1-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-15 13:53:31 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:

Description anil venkata 2017-10-13 06:40:48 UTC 
Description of problem:

When a keepalived is killed manually and then l3 agent is restarted, l3 agent is not spawning keepalived.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 anil venkata 2017-10-13 06:53:44 UTC 
When l3 agent is restarted, it sets HA network port status to DOWN because of https://code.engineering.redhat.com/gerrit/#/c/108938/ with the assumption that

1) server will notify port update to l2 agent and
2) then l2 agent will rewire the port and set status to ACTIVE. 
3) when port status is set to ACTIVE, server will notify l3 agent
4) when port status is ACTIVE, l3 agent will spawn keepalived

But in newton code base, I see step 1 not happening (i.e server notifying port update to l2 agent) because of that next steps also not happening and keepalived is never respawned.

But in upstream master code base, step 1 is happening because of OVO, and then all next steps, resulting in spawning keepalived.

I am investing now on how to notify l2 agent about this port update.
Comment 2 Alan Pevec 2017-10-16 11:13:07 UTC 
For the uninitiated like me: OVO := Oslo VersionedObjects [1]

[1] https://docs.openstack.org/neutron/latest/contributor/internals/objects_usage.html
Comment 4 anil venkata 2017-11-03 05:06:40 UTC 
Steps to reproduce:

1) Kill keepalived and immediately restart l3 agent
2) l3 agent should respawn keepalived
Comment 7 Toni Freger 2017-11-07 11:10:40 UTC 
Tested on openstack-neutron-9.4.1-5.el7ost.noarch

Verified according to provided steps.
I kill the process and restart the agent for several times, didn't see any issue, keeplalived process back to live each time
Comment 9 errata-xmlrpc 2017-11-15 13:53:31 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:3234