search

canonical / charm-openstack-service-checks

Collection of Nagios checks and other utilities that can be used to verify the operation of an OpenStack cluster
0 stars 2 forks source link

CRITICAL alert when floating ip is allocated but not associated #150

Closed sudeephb closed 6 months ago

sudeephb commented 6 months ago

When a floating IP is allocated to a project but not associated with a VM, nagios reports a CRITICAL alert.

$ /usr/local/lib/nagios/plugins/check_resources.py floating-ip --all CRITICAL: floating-ips 2/2 are DOWN

$ openstack floating ip show 10.51.16.120 -f yaml created_at: '2023-01-30T17:57:45Z' description: '' dns_domain: '' dns_name: '' fixed_ip_address: null floating_ip_address: 10.51.16.120 floating_network_id: f28a183a-9947-4daa-a5e0-cd019a3fbfc0 id: 97f5b0f7-5cc9-4f1d-bf80-1bb433757ee0 name: 10.51.16.120 port_details: null port_id: null project_id: bd8ff7c16b604636802feaf47e393a1e qos_policy_id: null revision_number: 4 router_id: null status: DOWN subnet_id: null tags: [] updated_at: '2023-01-30T19:47:54Z'

If there is no fixed_ip_address, a DOWN status should not be a critical alert. Maybe a WARNING or even INFO but definitely not CRITICAL.

Imported from Launchpad using lp2gh.