New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ListHypervisors() fails in v1.4.0 #191
Comments
@alexeymyltsev do you have a wallaby environment to test this on? |
@niedbalski unfortunately we do not have Wallaby, for this moment we just on Victoria. Looks like they move part of hypervisor's metrics to placement. |
Looks like with below code exporter will use only max version of microversion of Nova API.
I think will be better use variable from environment, if it is empty use max version. |
Nova API version 2.88 removed details from the os-hypervisors API [1]. These details are queried by openstack-exporter for metrics such as openstack_nova_running_vms. However, a change between v1.3.0 and v1.4.0 of the exporter caused it to use the latest API version, breaking collection of these metrics [2]. Starting from v1.5.0 of the exporter, OS_COMPUTE_API_VERSION can be set to configure the Nova API version to be used. Set it to 2.87 which is the maximum version still providing this data. [1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-wallaby [2] openstack-exporter/openstack-exporter#191 [3] openstack-exporter/openstack-exporter#201 Change-Id: I7605a3f9f74effb29ecec3b28e4709fd5f7f8cd4
Nova API version 2.88 removed details from the os-hypervisors API [1]. These details are queried by openstack-exporter for metrics such as openstack_nova_running_vms. However, a change between v1.3.0 and v1.4.0 of the exporter caused it to use the latest API version, breaking collection of these metrics [2]. Starting from v1.5.0 of the exporter, OS_COMPUTE_API_VERSION can be set to configure the Nova API version to be used. Set it to 2.79 (maximum in Train), which also fixes an issue displaying the flavor ID [4]. [1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-wallaby [2] openstack-exporter/openstack-exporter#191 [3] openstack-exporter/openstack-exporter#201 [4] openstack-exporter/openstack-exporter#220 Change-Id: I7605a3f9f74effb29ecec3b28e4709fd5f7f8cd4
Nova API version 2.88 removed details from the os-hypervisors API [1]. These details are queried by openstack-exporter for metrics such as openstack_nova_running_vms. However, a change between v1.3.0 and v1.4.0 of the exporter caused it to use the latest API version, breaking collection of these metrics [2]. Starting from v1.5.0 of the exporter, OS_COMPUTE_API_VERSION can be set to configure the Nova API version to be used. Set it to 2.79 (maximum in Train), which also fixes an issue displaying the flavor ID [4]. [1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-wallaby [2] openstack-exporter/openstack-exporter#191 [3] openstack-exporter/openstack-exporter#201 [4] openstack-exporter/openstack-exporter#220 Change-Id: I7605a3f9f74effb29ecec3b28e4709fd5f7f8cd4
With release v1.4.0 I am getting the following error:
This impacts 9 metrics that are collected by this function. Since it worked fine in v1.3.0, I tracked it down to the following code:
Removing this code fixes the error.
This is against a Wallaby deployment. Note the following change in Nova API for Wallaby:
The text was updated successfully, but these errors were encountered: