[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1458770
Title:
OvsdbMonitor module should respawn monitor only on specific failures
Status in neutron:
Expired
Bug description:
As of today, OvsdbMonitor used in neutron-openswitch-agent module, re-spawns
the monitor in case of any verb that appears on the stderr of the child monitor
process irrespective of the severity or relevance.
It is not ideal to restart child monitor process when the errors are not
fatal or error, such as warnings from a plugin driver that echos warnings to
the stderr etc.
And if such errors appears periodically, there are two side effects
a) Too frequent monitor processes could result in db.sock contention.
b) Frequent re-starts, would result in neutron agent missing interface
additions.
In ideal case, only fatal errors where it would effect the monitoring
or change detection on bridges ports and interfaces should result in
restart of the monitor, not like the case as it exists today.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1458770/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
