Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Known issues

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

• Tungsten Fabric known issues and limitations
  • Limitations
  • [10096] tf-control does not refresh IP addresses of Cassandra pods
  • [13755] TF pods switch to CrashLoopBackOff after a simultaneous reboot
  • [16241] Failure to update instance port through Horizon
• OpenStack known issues
  • [6912] Octavia load balancers may not work properly with DVR
  • [14678] Instance inaccessible through floating IP upon floating IP quick reuse
  • [16963] Ironic cannot provide nodes
  • [16495] Failure to reschedule OpenStack deployment pods after a node recovery
  • [16452] Failure to update the Octavia policy after policies removal
  • [16103] Glance client returns HTTPInternalServerError error
• StackLight known issues
  • [17045] fluentd-notifications does not track RabbitMQ credentials updates
  • [17573] OpenStack notifications missing in Elasticsearch and Kibana
• Cluster update known issues
  • [17477] StackLight in HA mode is not deployed or cluster update is blocked
  • [17305] Cluster update fails with the ‘Not ready releases: descheduler’ error
  • [16987] Cluster update fails at Ceph CSI pod eviction
  • [17115] Cluster update does not change releaseRefs in Cluster object for Ceph
  • [17038] Cluster update may fail with TimeoutError