[stein] Prometheus OpenStack Exporter Broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Committed
|
Medium
|
Keith Plant | ||
Stein |
Fix Committed
|
Medium
|
Keith Plant | ||
Train |
Fix Committed
|
Medium
|
Keith Plant |
Bug Description
**Bug Report**
What happened:
Two issues:
1. The clouds.yml template provided to prometheus-
2. The openstack-exporter version shipped in kolla stable/stein is 0.0.7 which does not retrieve stats for a standard stein deployment:
time="2019-
time="2019-
time="2019-
time="2019-
time="2019-
time="2019-
time="2019-
time="2019-
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x82827d]
goroutine 81 [running]:
main.(*
github.
created by github.
Setting "prometheus_
What you expected to happen:
It renders the clouds.yml template with the correct auth_url value and pulls stats correctly.
How to reproduce it (minimal and precise):
Set up a multi-region environment with the multi-region guide and set "enable_prometheus: yes"
https:/
**Environment**:
* OS (e.g. from /etc/os-release): CentOS Linux release 7.6.1810 (Core)
* Kernel (e.g. `uname -a`): 3.10.0-
* Docker version if applicable (e.g. `docker version`): 19.03.2
* Kolla-Ansible version (e.g. `git head or tag or stable branch` or pip package version if using release): 8.0.2.dev4
* Docker image Install type (source/binary): source
* Docker image distribution: centos
* Are you using official images from Docker Hub or self built? Official
* If self built - Kolla version and environment used to build: NA
* Share your inventory file, globals.yml and other configuration files if relevant
summary: |
- Prometheus OpenStack Exporter Auth URL Incorrect + [stein] Prometheus OpenStack Exporter Broken |
1. Makes sense, please propose a fix.
2. I have seen this raised a few times. There has been a suggestion of bumping the openstack exporter to 0.0.9 on stable/stein. This fixes a common issue, and I think is in line with our stable branch policy since it's not a major version bump.