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.

Update notes

This section describes the specific actions you need to complete to accurately plan and successfully perform the update. Consider this information as a supplement to the generic update procedures published in Operations Guide: Update to a patch version.

Cluster update schema

You can update to the 25.2.6 version from the following cluster versions (patch update):

  • 25.2 (2025-09-23)

  • 25.2.1 (2025-10-08)

  • 25.2.2 (2025-11-03)

  • 25.2.3 (2025-12-01)

  • 25.2.4 (2026-01-05)

  • 25.2.5 (2026-02-03)

For the detailed cluster update schema, refer to MOSK cluster update schema.

Patch update impact and maintenance windows planning

The following table provides details on the impact of a MOSK cluster update to a patch release within the 25.2 series.

Note

For the detailed workflow of update to a patch release, refer to Update to a patch version.

Expected update impact

Updated component

Impact on cloud users

Impact on cloud workloads

OpenStack and Tungsten Fabric

  • ~1% of read operations on cloud API resources may fail

  • ~8% of create and update operations on cloud API resources may fail

Open vSwitch networking - interruption of North-South connectivity, depending on the type of virtual routers used by a workload:

  • Distributed (DVR) routers - no interruption

  • Non-distributed routers, High Availability (HA) mode - interruption up to 1 minute, usually less than 5 seconds 0

  • Non-distributed routers, non-HA mode - interruption up to 10 minutes 0

Tungsten Fabric networking - no impact

Ceph

~1% of read operations on object storage API may fail

IO performance degradation for Ceph-backed virtual storage devices.

Host OS components

No impact

No impact
0(1,2)

You can bypass updating components of the cloud data plane to avoid the network downtime during Update to a patch version. By using this technique, you accept the risk that some security fixes may not be applied.

Known issues during the update

Before updating the cluster, be sure to review the potential issues that may arise during the process and the recommended solutions to address them, as outlined in Known issues: Cluster update.

Pre-update actions

There are no specific pre-update actions required when updating to version 25.2.6.

Post-update actions

There are no specific post-update actions required when updating to version 25.2.6.