Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

StackLight known issues

This section lists the StackLight known issues with workarounds for the Mirantis OpenStack for Kubernetes release 21.3.

[16353] Incorrect API availability calculation

OpenStack API availability data is shown in a 0 - 1 scale instead of an expected 0 - 100 scale.

As a workaround, manually set the extraQueries for OpenStack services API to * 100 in the StackLight Helm chart values of the Cluster release resource:

sfReporter:
 extraQueries:
   nova_api:
     title: 'Nova API'
     expr: 'avg(avg_over_time(openstack_api_check_status{service_name="nova"}[24h])) * 100'
   cinder_api:
     title: 'Cinder API'
     expr: 'avg(avg_over_time(openstack_api_check_status{service_name="cinderv2"}[24h])) * 100'
   glance_api:
     title: 'Glance API'
     expr: 'avg(avg_over_time(openstack_api_check_status{service_name="glance"}[24h])) * 100'
   keystone_api:
     title: 'Keystone API'
     expr: 'avg(avg_over_time(openstack_api_check_status{service_name="keystone"}[24h])) * 100'
   neutron_api:
     title: 'Neutron API'
     expr: 'avg(avg_over_time(openstack_api_check_status{service_name="neutron"}[24h])) * 100'