-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhos-18.0.1
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Moderate
During a deployment of the control plane I kept hitting an issue where the deployment would hang at creating the DNSmasq service definition. After beating my head against the failed deployment for longer than I care to admit, I found the error in the metallb-controller pod:
{"caller":"service.go:143","error":"can't change sharing key for \"openstack/dnsmasq-dns\", address also in use by openshift-storage/sts","level":"error","msg":"IP allocation failed","op":"allocateIPs","ts":"2024-11-19T20:13:47Z"}
634{"caller":"service_controller.go:112","controller":"ServiceReconciler","endpoints":"[]","event":"failed to handle service","level":"error","name":"openstack/dnsmasq-dns","service":"{\"kind\":\"Service\",\"apiVersion\":\"v1\",\"metadata\":{\"name\":\"dnsmasq-dns\",\"namespace\":\"openstack\",\"uid\":\"6fb2a08d-b7a0-47d7-90b8-af50d6186a71\",\"resourceVersion\":\"58937047\",\"creationTimestamp\":\"2024-11-19T19:33:45Z\",\"labels\":
{\"service\":\"dnsmasq\"},\"annotations\":{\"core.openstack.org/ingress_create\":\"false\",\"metallb.universe.tf/address-pool\":\"ctlplane\",\"metallb.universe.tf/allow-shared-ip\":\"ctlplane\",\"metallb.universe.tf/loadBalancerIPs\":\"172.20.85.80\"},\"ownerReferences\":[\{\"apiVersion\":\"network.openstack.org/v1beta1\",\"kind\":\"DNSMasq\",\"name\":\"dns\",\"uid\":\"942c5d73-14ea-448d-8501-6cae57ed24e8\",\"controller\":true,\"blockOwnerDeletion\":true}],\"managedFields\":[{\"manager\":\"manager\",\"operation\":\"Update\",\"apiVersion\":\"v1\",\"time\":\"2024-11-19T20:13:47Z\",\"fi...
635
"
Nooba-STS and Nooba-s3 had been assigned IPs randomly from the Openstack subnet pools I had created. The same IP I had intended to use for my ctlplane VIP(172.20.85.80) had been assigned to nooba-sts. There were no obvious errors in the Openstack namespace and the deployment would just hang. I had installed ODF prior to installing metallb or defining any IP pools.