Add detection of missing metadata service to OpenStack service checks
Bug #1846133 reported by
Paul Goins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-openstack-service-checks |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
We encountered a problem on a cloud where instances were successfully setting up network routes roughly 50% of the time. This was due to a missing metadata proxy on one of the DHCP agents.
This log message was detected in cloud-init output as one of the instances was being created:
[ 31.695675] cloud-init[783]: 2019-09-26 16:30:46,217 - util.py[WARNING]: No active metadata service found
We should add a check to our Rally checks so that we can detect this message and trigger an alert on it.
| Changed in charm-openstack-service-checks: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Eric Chen (eric-chen) wrote | #1 |
| Changed in charm-openstack-service-checks: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
This charm is no longer being actively maintained. Please consider using the new Canonical Observability Stack instead.
(https:/
I will close this feature request