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.

Addressed issues

The following issues have been addressed in the MOSK 22.5 release:

  • [26773] Fixed the issue with VM autoscaling failure when using the CPU-related metrics in Telemetry.

  • [26534] Fixed the issue with the ironic-conductor Pod getting stuck in the CrashLoopBackOff state after the Container Cloud management cluster upgrade from 2.19.0 to 2.20.0. The issue occurred due to the race condition between the ironic-conductor and ironic-conductor-http containers of the ironic-conductor Pod that tried to use ca-bundle.pem simultaneously but from different users.

  • [25594][Yoga] Fixed the issue with security groups shared through RBAC not being filtered and used by Nova to create instances due to the OpenStack known issue #1942615.

    Note

    The bug still affects OpenStack Victoria and is fixed for OpenStack Yoga.

  • [24435] Fixed the issue with MetalLB speaker failing to announce the LB IP for the Ingress service after the MOSK cluster update.

    For existing clusters, you can set externalTrafficPolicy back from Cluster to Local after updating to 22.5. For details, see Post-upgrade actions.