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.

Switch to latest✕

Known issues

This section describes the MOSK known issues with available workarounds. For the known issues in the related version of Mirantis Container Cloud, refer to Mirantis Container Cloud: Release Notes.

• OpenStack known issues
  • [25124] MPLSoGRE encapsulation has limited throughput
  • [31186,34132] Pods get stuck during MariaDB operations
  • [34897] Machines are not available after Victoria to Wallaby update
  • [42386] A load balancer service does not obtain the external IP address
• Tungsten Fabric known issues
  • [37684] Cassandra containers are experiencing high resource utilization
  • [30738] ‘tf-vrouter-agent’ readiness probe failed (No Configuration for self)
  • [13755] TF pods switch to CrashLoopBackOff after a simultaneous reboot
• Wireguard known issues
  • [35147] The Wireguard interface does not have the IPv4 address assigned
• Cluster update known issues
  • [35111] openstack-operator-ensure-resources job stuck in CrashLoopBackOff
  • [37012] Masakari failure during update