Monitor Metadata agent health via the HTTP layer

Bug #1921653 reported by Edin S
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Neutron Open vSwitch Charm
New
Undecided
Unassigned
charm-ovn-chassis
New
Undecided
Unassigned

Bug Description

We've found a few cases (e.g. LP#1907686) where monitoring the the wellness of the systemd service "nova-api-metadata" to be inadequate in determining if the metadata service is working; the systemd service might be reported as active/running, but it may be failing to receive and respond to connections/requests.

I'd like to request a check for monitoring a metadata agent's health via the HTTP layer (e.g. make a request to http://169.254.169.254/ and potentially check for good values). I understand that there are complexities that arise from network namespaces, and scaling this solution to hundreds (or thousands) of networks -- but perhaps there's a middle ground that can be found.

Edin S (exsdev)
description: updated
Edin S (exsdev)
description: updated
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.