Addressed issues

The following issues have been addressed in the MOSK 26.1.1 release:

  • [LCM] [56677] Resolved the issue that prevented management node replacement when automated node cleaning failed.

  • [LCM] [60956] Added /var/log/warn into the logrotate configuration to prevent disk space issues.

  • [OpenSDN] [62314] Resolved the issue that caused failure to add a new BGP router using the OpenSDN web UI.

  • [OpenSDN] [62399] Resolved the issue that caused the DNS backend to split during recreation of a virtual machine with the same DNS name.

  • [OpenStack] [56111] [Epoxy] Resolved the issue that caused server rebuild to fail with VirtualInterfaceCreateException (fault code 500) due to a race condition triggered by Nova creating Neutron ports without device_owner. Without it, Neutron skipped DHCP provisioning and later changed the port status to ACTIVE during instance teardown, causing both initial builds and rebuilds to enter the ERROR state.

  • [OpenStack] [Epoxy] [OVS] [58690] Resolved the issue that caused floating IP deletion to fail due to NotFound errors from Designate when deleting PTR records or zones.

  • [OpenStack] [Epoxy] [59184] Resolved the issue that caused Horizon to incorrectly display DHCP as enabled for a subnet in the Subnet Details tab of the Edit Subnet dialog when DHCP was actually disabled.

  • [OpenStack] [Epoxy] [59296] Resolved the issue that caused creation of a server with security groups attached to fail when a project contained multiple security groups with the same name.

  • [OpenStack] [Epoxy] [60381, 61640] Improved Pure Storage support in the Block Storage service (OpenStack Cinder).

  • [Ceph] [60923] Resolved the issue that caused Ceph OSD to ignore multipath devices with metadata devices and leave them unconfigured regardless of being discovered.

  • [Cluster update] [59171] Resolved the issue that caused the sync operation to fail with the Size mismatch and Digest mismatch errors during the preparation of an offline copy for an air-gapped cluster update.

  • [Management console] [58691] Resolved the issue where updating tlsConfig using the MOSK management console incorrectly set dedicatedControlPlane: true.