To Reproduce Steps to reproduce the behavior:

1. Trigger ovn control and dataplane minor update
2. wait for MinorUpdateOVNDataplane to be completed
3. proceed to controlplane and dataplane update
4. can see MinorUpdateOVNDataplane going again in progress

Expected behavior

• The status should be consistent

Bug impact

• It causes confusion on the minor update status, even though final dataplane is stuck, control plane status shows minor update of ovn is in progress

Known workaround

• Status become consistent when full minor update is finished.

Additional context

• Slack thread https://redhat-internal.slack.com/archives/C04J1D40W4W/p1767966293720519?thread_ts=1767957381.565749&cid=C04J1D40W4W 
• https://github.com/openstack-k8s-operators/openstack-operator/blob/4648b0452b75d1b2e20cd96cf3e602592e5bc38e/internal/openstack/dataplane.go#L46-L48 check looks unnecessary, also https://github.com/openstack-k8s-operators/openstack-operator/blob/4648b0452b75d1b2e20cd96cf3e602592e5bc38e/internal/openstack/dataplane.go#L41-L43 seems unnecessary too as we not updating nodeset during minor update.