This is a follow up from https://issues.redhat.com/browse/OSPRH-6672

This is caused by infra-operator ordering the network names alphabetically and in go StorageMgmt is smaller than ctlplane.
https://github.com/openstack-k8s-operators/infra-operator/blame/main/controllers/network/ipset_controller.go#L278-L281

As a WA only lower case network names should be used in the NodeSet and the name of the network names after golang shorting should result in ctlplane being the first.

The real solution could be to drop the lexicographical ordering of ip reservations, the infra-operator should keep the reservation order as is without reordering. The dataplane-operator can implement a validation webhook that ensures that the first network in the NodeSet is always ctlplane.

See the slack discussion as well https://redhat-internal.slack.com/archives/CQXJFGMK6/p1714474966545229

The lexicographical ordering of ip reservation is removed from infra-operator via https://github.com/openstack-k8s-operators/infra-operator/pull/221 so the order of the networks are preserved as provided by the user.

However this still allows to pass the networks in the wrong order. If the ctlpane network is not the first network then the live migration will still fail with the same reason.