Neutron OCF scripts should use neutron agent-list to check status

Bug #1528340 reported by Miroslav Anashkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Opinion
High
Matthew Mosesohn
5.1.x
Opinion
High
Matthew Mosesohn
6.0.x
Opinion
High
Matthew Mosesohn
6.1.x
Opinion
High
Matthew Mosesohn
7.0.x
Opinion
High
Matthew Mosesohn
8.0.x
Won't Fix
High
Matthew Mosesohn

Bug Description

We have cases when Neutron agent managed by Pacemaker was reported by `neutron agent-list` as dead but Pacemaker considered it as alive.
This happens when agent process exists and get stalled, for instance, due to Oslo messaging bug.
Built-in Neutron heartbeat functionality detects such agents as dead correctly.

Maciej Relewicz (rlu)
tags: added: area-mos
summary: - Make OCF scripts for Neutron agents capable of checking the agent status
- through Neutron
+ Neutron OCF scripts should use neutron agent-list to check status
tags: added: ha team-bugfix
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

This is a bugfix team bug. Sorry, Alexey

Dmitry Pyzhov (dpyzhov)
tags: added: area-library
removed: area-mos
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

This _must_ not be addressed.

Any kind of possible fix will do much more harm than good.
While neutron agent-list is a good way to tell if neutron-server should keep resources on particular agent (like DHCP or L3), it absolutely can't be a basis for decision of agent restart.

The roots of this bug is oslo.messaging issue where agents stopped communicating via RPC until restart.
The problem is not specific to neutron agents (nova, cinder services are affected too).
Adding protection from such kind of bugs, especially a kind of protection which can be buggy in the similar way is plain wrong both from theoretical and practical point of view.

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I agree with Eugene

Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

If both Eugene and Bogdan agree that this is a bad fix, I'm afraid I will have to side with them. Let's leave this as-is

Changed in fuel:
milestone: 8.0 → 9.0
tags: added: wontfix-risky
Changed in fuel:
milestone: 9.0 → 9.0-updates
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.