Add check for duplicate HA routers

Bug #1820762 reported by Drew Freiberger
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
charm-openstack-service-checks
Won't Fix
Wishlist
Unassigned

Bug Description

There are sometimes race conditions with VRRP and keepalived with DVR and HA router implementations.

To handle this, we should alert on routers on HA enabled router sites which are running on more or less than 1 active node and configured on less than or more than min/max ha routers.

Here is a handy gist to check for HA routers that have dupe avail:

https://gist.githubusercontent.com/dosaboy/afc40bf31b784a4dd552f7f5569dc7ee/raw/ad52b67b158d771b3f965141fca10143e7b89d56/check_router_l3agent_ha_status.sh

This can be massaged into an NRPE check with some amount of ease.

Revision history for this message
Mihaela Andronic (mihaela) wrote :

Hi,

We have been using this check in out installs and have noticed that it checks for duplicates but not for the 0 condition. It would be a good idea to make sure it check that the routers have at least one agent hosting it. We've run into an issue with one router not having any l3 agents hosting it and no alerts whatsoever for the case.

Thank you,
Kind Regards

tags: added: canonical-bootstack
Xav Paice (xavpaice)
Changed in charm-openstack-service-checks:
assignee: Legacy - Canonical WTFB (canonical-bootstack) → nobody
importance: Undecided → Wishlist
status: New → Triaged
Jeremy Lounder (jldev)
Changed in charm-openstack-service-checks:
status: Triaged → New
status: New → Triaged
Eric Chen (eric-chen)
Changed in charm-openstack-service-checks:
status: Triaged → Won't Fix
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.