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 4 forks source link

Nagios reports WARNING for s3 checks with Status Information "HTTP WARNING: HTTP/1.1 404 Not Found - 444 bytes in 0.003 second response time" #4

Open sudeephb opened 10 months ago

sudeephb commented 10 months ago

focal-ussuri, charms revision 20.10

Nagios reports WARNING for s3 checks with Status Information "HTTP WARNING: HTTP/1.1 404 Not Found - 444 bytes in 0.003 second response time" for all endpoints: admin, internal and public.

It looks like checking /healthcheck does no longer work.

ubuntu@juju-496933-1-lxd-8:/etc/nagios/nrpe.d$ cat check_s3_public.cfg

check s3_public

The following header was added automatically by juju

Modifying it will affect nagios monitoring and alerting

servicegroups: juju

command[check_s3_public]=/usr/lib/nagios/plugins/check_http -H 10.100.44.31 -p 80 -u /healthcheck

ubuntu@juju-496933-1-lxd-8:/etc/nagios/nrpe.d$ /usr/lib/nagios/plugins/check_http -H 10.100.44.31 -p 80 -u /healthcheck HTTP WARNING: HTTP/1.1 404 Not Found - 444 bytes in 0.003 second response time |time=0.002714s;;;0.000000;10.000000 size=444B;;;0

But checking / works fine:

ubuntu@juju-496933-1-lxd-8:/etc/nagios/nrpe.d$ /usr/lib/nagios/plugins/check_http -H 10.100.44.31 -p 80 -u / HTTP OK: HTTP/1.1 200 OK - 432 bytes in 0.004 second response time |time=0.003760s;;;0.000000;10.000000 size=432B;;;0

Imported from Launchpad using lp2gh.

sudeephb commented 10 months ago

(by phausman) Subscribing ~field-critical as this issue occurs on a customer deployment and no workaround is known yet.

sudeephb commented 10 months ago

(by billy-olsen) The llama-charmers-next version of the charm has the s3_check_params config option [0] which would allow you to change this. A workaround would be to deploy that version and specify the s3_check_params value to the value you want.

I suspect that this is due to the next versions of the LMA charms have not yet been published. Since a work-around exists and the LMA charms are best-effort field SLA, I am reducing this to field-high.

[0] https://jaas.ai/u/llama-charmers-next/openstack-service-checks/9#charm-config-s3_check_params

sudeephb commented 10 months ago

(by phausman) hi billy-olsen, I can confirm that using -next version of the charm and configuring s3_check_params: "/" solves the problem.

Thank you!

sudeephb commented 10 months ago

(by guoqiao) Fix already in llama-charmers-next, just need to release that to main.