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.
Addressed issues¶
The following issues have been addressed in the MOSK 25.1.1 release:
Cluster update¶
[46671] Resolved the issue that caused the cluster update failure with the
tf-config
pods crashed.[49078] Resolved the issue that caused migration to containerd to get stuck due to orphaned Docker containers.
[51887] Resolved the issue that caused continuous restart of the Rockoon controller pod.
[52414] Resolved the issue that resulted in the missing status in the
nodeworkloadlock
objects for OpenStack.
OpenStack¶
[47695] Resolved the issue encountered during an OpenStack upgrade to Caracal, where the Block Storage service failed due to database migration issues with the
use_quota
column in volumes.[50218] Resolved the issue when Octavia health manager remained stuck in initialization after a node replacement.
[50630] Resolved the issue that caused the
ironic-conductor
pod to fail to start after powering a node off and then on again.[53764] Resolved the issue that prevented the
openstack-nova
chart from application after adding node overrides to theOpenStackDeployment
custom resource.[53813] Resolved the issue in the
os-brick
in the Antelope release that prevented updating the volume size if the volume was resized without detaching and multipath was enabled.
Networking¶
[52259] [Tungsten Fabric] Resolved the issue that prevented adjusting the Kubernetes resources causing OOM on the Tungsten Fabric control nodes.
[52410] [OVS] Resolved the issue that caused the unexpected restart of Open vSwitch pods during external proxy removal.
StackLight¶
[49340] Resolved the issue that caused failure of tag-based log filtering using the
tag_include
parameter forlogging.externalOutputs
whenoutput_kind: audit
was selected.
Bare metal¶
[49678] Resolved the issue that caused the flapping status (
Configure
→Ready
→Configure
→Ready
) of machines where anyHostOSConfiguration
object was targeted and migration to containerd was applied.