openstack exporter nova_server_status fails to return flavor id

[jheikki100]

We are trying to get openstack metrics to Prometheus for further accounting data processing with cloudkitty.
However, when I query prometheus metrics from openstack exporter

openstack_nova_server_status field flavor_id is always returning <nil> in prometheus openstack exporter.

For example:

openstack_nova_server_status{address_ipv4="",address_ipv6="",availability_zone="nova",flavor_id="<nil>",host_id="34473036769974153a388fb747e773fd7aa6095e48c6e23096b105c1",h
ypervisor_hostname="bm-compute01-lm",id="4177d13c-d42b-499c-a917-c76d2dc75226",name="demo-jhtest",status="ACTIVE",tenant_id="960168fa6ffd4b1d8d6007c3f234fa6c",user_id="d4fe
783e96a743fdba7d207b519802c7",uuid="4177d13c-d42b-499c-a917-c76d2dc75226"} 0

It seems that Prometheus is aware of flavors because direct query
curl 'http:https://prometheus_host:9091/api/v1/label/flavor_id/values
returns list where values correspond to existing flavor ids in OpenStack.

Our OpenStack instance is currently on Wallaby release and is based on Kolla-Ansible.

Looking forward for suggestions or a fix because we really need the flavor_id in downstream accounting processing.

[engel75]

Same problem with rocky. Output of v1.1.0 vs v1.5.0:

v1.1.0
openstack_nova_server_status{address_ipv4="",address_ipv6="",availability_zone="ch-zh1-az2",flavor_id="xxxxx-4a78-8dc0-206deexxxxxxxx",host_id="c3165b602471b79356d6210a2775b0f6c9b268065292aff84a2615d8",id="xxxxxxxx",name="test-u1804-az2",status="ACTIVE",tenant_id="yyyyyyyyyyyyyyy",user_id="zzzzzzzzzzzz",uuid="idididididid"} 0

v1.5.0
openstack_nova_server_status{address_ipv4="",address_ipv6="",availability_zone="ch-zh1-az2",flavor_id="<nil>",host_id="c3165b602471b79356d6210a2775b0f6c9b268065292aff84a2615d8",hypervisor_hostname="xxxxxxxxxx",id="bee90dce-6256-4b64-82be-380fb6b5557f",name="test-u1804-az2",status="ACTIVE",tenant_id="yyyyyyyyy",user_id="zzzzz",uuid="idididididid"} 0

[gtherond]

That's because the way the flavor are returned by the API changed with a microversion and that microversion was promoted as the minimum version for victoria.

Horizon had the same issue up to 18.6.4 that was recently patched: https://bugs.launchpad.net/horizon/+bug/1940834

[priteau]

I believe this changed with microversion 2.47: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id43

Replace the flavor name/ref with the actual flavor details from the embedded flavor object when displaying server details. Requests made with microversion >= 2.47 will no longer return the flavor ID/link but instead will return a subset of the flavor details. If the user is prevented by policy from indexing extra-specs, then the extra_specs field will not be included in the flavor information.

[priteau]

Same problem with rocky. Output of v1.1.0 vs v1.5.0:

v1.1.0
openstack_nova_server_status{address_ipv4="",address_ipv6="",availability_zone="ch-zh1-az2",flavor_id="xxxxx-4a78-8dc0-206deexxxxxxxx",host_id="c3165b602471b79356d6210a2775b0f6c9b268065292aff84a2615d8",id="xxxxxxxx",name="test-u1804-az2",status="ACTIVE",tenant_id="yyyyyyyyyyyyyyy",user_id="zzzzzzzzzzzz",uuid="idididididid"} 0

v1.5.0
openstack_nova_server_status{address_ipv4="",address_ipv6="",availability_zone="ch-zh1-az2",flavor_id="<nil>",host_id="c3165b602471b79356d6210a2775b0f6c9b268065292aff84a2615d8",hypervisor_hostname="xxxxxxxxxx",id="bee90dce-6256-4b64-82be-380fb6b5557f",name="test-u1804-az2",status="ACTIVE",tenant_id="yyyyyyyyy",user_id="zzzzz",uuid="idididididid"} 0

Since v1.4.0, openstack-exporter will use the latest Nova API microversion, which means any OpenStack cloud running Pike or newer will see this behaviour.

You can use the OS_COMPUTE_API_VERSION environment variable to configure the Nova API microversion to use. Set it to version 2.46 or any other below and flavor_id will be included as before.

[gtherond]

But still, this doesn't fix the fact that exporter don't catch up latest available information/data from the new API microversion.
Shouldn't the exporter rather fix min/max microversion it support itself for each release rather?