Trilio dmapi fails with Bad Request because of missing -S setting on check_http

[Pedro Guimarães]

This bug refers to dmapi service (there was a bug related to Trilio Vault's certificate missing: https://bugs.launchpad.net/charm-openstack-service-checks/+bug/1842748)

In this case, I am running Trilio's datamover API with certificates.

I am getting a 400 Bad Request on chek_http since it is running without -S option:

$ /usr/lib/nagios/plugins/check_http -H TRILIO_API -p 8784 -u /
HTTP WARNING: HTTP/1.1 400 Bad Request - 643 bytes in 0.003 second response time |time=0.003284s;;;0.000000 size=643B;;;0

$ /usr/lib/nagios/plugins/check_http -H TRILIO_API -p 8784 -u / -S
HTTP OK: HTTP/1.1 200 OK - 340 bytes in 0.016 second response time |time=0.015796s;;;0.000000 size=340B;;;0

Seems openstack-service-checks did not learn about dmapi's certificates.

It is important to state that, originally, dmapi was running without certificates and we moved to https post-deployment.

[Eric Chen (eric-chen)]

Migrate to https://github.com/canonical/charm-openstack-service-checks/issues