Bug 1989700

Description of problem:
Metallb does not assign an IP address to the service if there is a service on the cluster with static IP address even though the address pool has available IP address.

Remove the service configured with static IP address, the loadbalancer service immediately gets the IP address assigned from the address pool.



Version-Release number of selected component (if applicable):
4.9

How reproducible:
Always

Steps to Reproduce:
1. Install the loadbalancer on vSphere cluster with metallb operator
2. Create a address pool with two ip address available to be assigned to services.

apiVersion: metallb.io/v1alpha1
kind: AddressPool
metadata:
  name: address-pool-silver
  namespace: metallb-system
spec:
  protocol: layer2
  addresses:
    - 172.31.249.160 - 172.31.249.160
    - 172.31.249.220 - 172.31.249.220

3. Create a loadbalancer service in project a1 with the following yaml (hello-world.yaml) to see it successfully get an IP address assigned to it.
---------------------
apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: hello-world
  labels:
    app: hello-world
spec:
  selector:
    matchLabels:
      app: hello-world
  replicas: 2
  template:
    metadata:
      labels:
        app: hello-world
    spec:
      containers:
      - name: hello-world
        image: gcr.io/google-samples/node-hello:1.0
        imagePullPolicy: Always
        ports:
        - containerPort: 8080
          protocol: TCP
 
---
apiVersion: v1
kind: Service
metadata:
  name: hello-world
spec:
  selector:
    app: hello-world
  ports:
  - port: 80
    targetPort: 8080
    protocol: TCP
  type: LoadBalancer

NAME          TYPE           CLUSTER-IP       EXTERNAL-IP      PORT(S)        AGE
hello-world   LoadBalancer   172.30.204.132   172.31.249.160   80:31317/TCP   14h

4. Edit network cluster object to provide allowed CIDR range.

oc edit network.config.openshift.io cluster -o yaml
spec:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  externalIP:
    policy:
      allowedCIDRs:
      - 172.31.249.10/24


5. Create another load balancer service with static Ip address in project a2 with YAML (hello.idle.yaml) below:-
------
apiVersion: v1
kind: List
items:
- apiVersion: v1
  kind: ReplicationController
  metadata:
    labels:
      name: hello-idle
    name: hello-idle
  spec:
    replicas: 2
    selector:
      name: hello-idle
    template:
      metadata:
        labels:
          name: hello-idle
      spec:
          containers:
          - image: quay.io/openshifttest/hello-pod@sha256:04b6af86b03c1836211be2589db870dba09b7811c197c47c07fbbe33c7f80ef7
            name: hello-idle
            ports:
            - containerPort: 8080
              protocol: TCP
            resources:
              limits:
                cpu: 200m
                memory: 256Mi
              requests:
                cpu: 100m
                memory: 256Mi
            terminationMessagePath: /dev/termination-log
          dnsPolicy: ClusterFirst
          restartPolicy: Always
          securityContext: {}
          terminationGracePeriodSeconds: 30
- apiVersion: v1
  kind: Service
  metadata:
    name: hello-idle
  spec:
    ports:
    - port: 80
      targetPort: 8080
      protocol: TCP
    selector:
      name: hello-idle
    type: LoadBalancer
    externalIPs: 
    - 172.31.249.10



6. Create another loadbalancer service with YAML in step#3 in project a3.

oc create -f hello-world.yaml


Actual results:
Service does not get IP address assigned.
NAME          TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
hello-world   LoadBalancer   172.30.226.205   <pending>     80:30863/TCP   118m


Expected results:

Service should get an IP address assigned.

Additional info:
NAME            CSV                                   APPROVAL    APPROVED
install-8d5v2   metallb-operator.4.9.0-202108021529   Automatic   true
Server Version: 4.9.0-0.nightly-2021-08-02-145924
Kubernetes Version: v1.21.1+8268f88