To Reproduce Steps to reproduce the behavior:

1. Deploy control plane.
2. Try to deploy data plane with OpenStackDataPlaneNodeSet name length less than 53 characters but bigger than 28 characters.
3. See error of invalid batch for job provisionserver-checksum-discovery due to container's name size being bigger than 63 characters [1].

Expected behavior

• Customer be able to use a name with length of 53 characters.

Device Info (please complete the following information):

• OpenShift Cluster Version: 4.18.30
• OpenStack Operator Version: 1.0.18
• Deployed Version: 18.0.15-20251126.192455

Bug impact

• Customer is unable to deploy dataplane.

Known workaround

• Reduce the OpenStackDataPlaneNodeSet name length.

Additional context

• https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_red_hat_openstack_services_on_openshift/index#proc_creating-an-OpenStackDataPlaneNodeSet-CR-with-preprovisioned-nodes_dataplane 

• [1]
  2026-01-01T18:51:26Z ERROR controllers.OpenStackProvisionServer Job CreateOrPatch failed {"job": "0123456789-openstack-data-plane-provisionserver-checksum-discovery", "error": "Job.batch \"0123456789-openstack-data-plane-provisionserver-checksum-discovery\" is invalid: [spec.template.labels: Invalid value: \"0123456789-openstack-data-plane-provisionserver-checksum-discovery\": must be no more than 63 characters, spec.template.spec.containers[0].name: Invalid value: \"0123456789-openstack-data-plane-provisionserver-checksum-discovery\": must be no more than 63 characters]"}

• https://github.com/openstack-k8s-operators/openstack-baremetal-operator/blob/main/internal/openstackprovisionserver/job.go