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 25.2 release:

  • [OpenStack] [53249] Fixed an issue that caused Horizon to fail to start when resolving Memcached in the event of the controller failure.

  • [TF] [53831] Addressed the issue that caused critical components such as tf-config and tf-config-db to repeatedly crash after restoration of Tungsten Fabric database from a backup in clusters that have undergone at least one major or patch cluster update.

  • [Core] [50622] Addressed the issue that prevented any user except m:kaas@management-admin to access or modify BareMetalHostInventory objects.

  • [Bare metal] [50287] Addressed the issue that prevented a BareMetalHost object with a Redfish Baseboard Management Controller address to pass the registering phase.

  • [LCM] [50819,51134] Addressed the issue that prevented clusters from entering or exiting maintenance mode if a granular update was started using the ClusterUpdatePlan object.

  • [LCM] [50768] Addressed the issue that prevented successful editing of the MCCUpgrade object, which contained the Internal error failed to call webhook: the server could not find the requested resource when trying to save changes in the object.

  • [LCM] [50636] Addressed the issue that caused the nfs-common package to be deleted during MOSK cluster update. This package is no longer automatically removed from cluster nodes if a MOSK cluster is deployed with the MariaDB backup hosted on an external NFS backend.

  • [LCM] [50561] Addressed the issue that caused the local-volume-provisioner pod to switch to the CrashLoopBackOff state on a machine that was disabled and consequently re-enabled.

  • [Cluster update] [51339] Addressed the issue that caused cluster update to be blocked if at least one node of any cluster was not rebooted while applying the update.

  • [StackLight] [53802, 52253] Addressed the issue that resulted in the telegraf-ds-smart pod constantly restarting with OOM kill messages on every compute node while smartctl was trying to scan all attached iSCSI volumes.

  • [StackLight] [51145] Addressed the issue that caused the PrometheusTargetScrapesDuplicate alert to permanently fire on a management cluster that has sf-notifier enabled.

  • [Ceph] [50637] Addressed the issue that caused Ceph to create a second miracephnodedisable object if some node was disabled at the same time with the ceph-maintenance-controller restart.

  • [Ceph] [50566] Addressed the issue that caused Ceph upgrade to run very slow during patch or major cluster update due to the upstream Ceph issue 66717.

  • [Management console] [53886] Addressed the issue that caused the failure of moving a worker machine into maintenance mode with the Only undefined workers can be in maintenance mode at the same time error.

  • [Management console] [50181] Addressed the issue that prevented deployment of a compact MOSK cluster through the MOSK management console due to inability to add any label to the control plane machines along with inability to change dedicatedControlPlane: false.

  • [Management console] [50140] Addressed the issue that prevented the Clusters page for the bare metal provider to display information about the Ceph cluster in the Ceph Clusters tab.