The following issues have been addressed in the MOSK 23.3 release:
[OpenStack]  Resolved the issue that caused the unavailability of machines from the nodes with DPDK after update of OpenStack from Victoria to Wallaby.
[OpenStack]  Resolved the issue with an incorrect port value for RabbitMQ after update.
[Update]  Resolved the issue that caused the openstack-operator-ensure-resources job getting stuck in
[WireGuard]  Resolved the issue that prevented the WireGuard interface from having the IPv4 address assigned
[Bare metal]  Resolved the issue that caused a failure of the etcd pods due to the simultaneous deployment of several pods on a single node. To ensure that etcd pods are always placed on different nodes, MOSK now deploys etcd with the
StackLight  Resolved the issue with
ucp-node-exporter. It was unable to bind port 9100, causing the
ucp-node-exporterstart failure. This issue was due to a conflict with the StackLight
node-exporter, which was also binding the same port.
The resolution of the issue involves an automatic change of the port for the StackLight
node-exporterfrom 9100 to 19100. No manual port update is required.
If your cluster uses a firewall, add an additional firewall rule that grants the same permissions to port 19100 as those currently assigned to port 9100 on all cluster nodes.