The following issues have been addressed in the MOSK 22.4 release:
[Update] Fixed the issue causing MOSK cluster update failure after an OpenStack controller node replacement.
[OpenStack] Fixed the issue with
l3-agentbeing stuck in the
Not readystate and routers not being initialized properly during Neutron restart.
[OpenStack] Fixed the issue that caused a Masakari instance evacuation to fail if an encrypted volume was attached to a node.
[OpenStack] Fixed the issue that caused some Masakari instances to get stuck in the
Errorstate when being migrated to a new OpenStack compute node during host evacuation. The issue occurred on OpenStack compute nodes with a large number of instances.
[OpenStack] Fixed the issue wherein Octavia load balancers provisioning, and, occasionally, the listeners or pools associated with these load balancers got stuck in the
[OpenStack] Implemented the capability to enable
trustedmode for SR-IOV ports.
[StackLight] Introduced projects filtering by a domain name for the
defaultdomain to fix the issue wherein a wrong project was chosen by name in case of multiple projects with the same names.
[Ceph] Implemented the capability to parametrize the RADOS Block Device (RBD) device map to avoid Ceph volumes being unresponsive due to a disabled cyclic redundancy check (CRC) mode. Now you can use the
rbdDeviceMapOptionsfield in the Ceph pool parameters of the
KaaSCephClusterCR to specify custom RBD map options to use with
StorageClassof a corresponding Ceph pool. For details, see Container Cloud documentation: Ceph pool parameters.
 [Ceph] Fixed the issue causing Ceph conditon stuck in absence of the Ceph cluster secrets information. If you applied the workaround to your MOSK 22.3 cluster before the update, remove the
versionparameter definition from
KaaSCephClusterafter the managed cluster update because the Ceph cluster version in MOSK 22.4 updates to 15.2.17.