Charm-helpers has stable git branches that need to run the CI (github
actions workflow) too.
(cherry picked from commit b26627541bfb62e5f5a1e747715b315b835e3d88)
* Update Makefile to be consistent with CI (#777)
Also remove python3.5 from the CI build,
because that is no longer supported in charm-helpers,
and use a supported runs-on ubuntu version for github CI.
(cherry picked from commit 59f134b7d8b0b918ac71cbac8aa641e21babbdee)
* Pep8 fixes.
(cherry picked from commit a085ade940264a774716e43aae2c8327f26526ad)
* Pin dnspython to sensible versions
* Use yaml.safe_load()
---------
Co-authored-by: Samuel Walladge <email address hidden>
When all the servers configured in the system failed to answer the query
the exception `dns.resolver.NoNameservers` is raised while NXDOMAIN is
only for when the name was not found.
(cherry picked from commit 91ee22fbe3c6fbe8b3b2b60371b43ad0a3c67f92)
This change adds the option of running HTTPS health checks. It is
proposed in the context of LP: #1946280 where the backend radosgw server
can be configured to run in https mode.
We disable certificate verification because we are only interested in
the health of the service.
Ease KeepAliveTimeout in line with keystoneauth1.session.Session
Apache2's default value for KeepAliveTimeout is 5 seconds, which is okay
for general web-page serving use cases. However, sessions and connection
pools created by keystoneauth1.session.Session can be terminated
unnecessarily during multiple API calls in a session due to the short
KeepAliveTimeout.
Let's ease KeepAliveTimeout to 75 seconds, which is fairly standard for
API services behind a reverse proxy since it's the default value of
nginx.
Closes-Bug: #1947010
(cherry picked from commit 9a5bf40790080362cf340692b8992f31a6750cda)
