CreatingLoadBalancerFailed after the second update of the value "service.beta.kubernetes.io/oci-load-balancer-tls-secret"

[algora]

Versions

Environment:

• Kubernetes version : Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.10", GitCommit:"575467a0eaf3ca1f20eb86215b3bde40a5ae617a", GitTreeState:"clean", BuildDate:"2019-12-11T12:32:32Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

I created a load balancer with:

apiVersion: v1
kind: Service
metadata:
  name: lb-http
  annotations:
    service.beta.kubernetes.io/oci-load-balancer-backend-protocol: HTTP
    service.beta.kubernetes.io/oci-load-balancer-security-list-management-mode: None
    service.beta.kubernetes.io/oci-load-balancer-shape: 400Mbps
    service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443"
    service.beta.kubernetes.io/oci-load-balancer-subnet1: internal-subnet
    service.beta.kubernetes.io/oci-load-balancer-subnet2: internal-subnet
    service.beta.kubernetes.io/oci-load-balancer-tls-secret: secret-1
    service.beta.kubernetes.io/oci-load-balancer-internal: "true"
spec:
  type: LoadBalancer
  ports:
    - name: http
      port: 80
      targetPort: 80
    - name: https
      port: 443
      targetPort: 8008
  selector:
    app.kubernetes.io/instance: myservice
    app.kubernetes.io/name: myservice

After the LB was created I updated service.beta.kubernetes.io/oci-load-balancer-tls-secret to be secret-2, and the LB was ensured.

Afterwards I updated service.beta.kubernetes.io/oci-load-balancer-tls-secret to be again secret-1, and the following error appeared in the svc describe of the LB: Warning CreatingLoadBalancerFailed 7s (x12 over 23m) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service <namespace>/<resource name>: updating listener: Service error:InvalidParameter. Default Listener on port '443' refer to VIP 'private-vip' twice. http status code: 400

The issue was mentioned in the comment https://github.com/oracle/oci-cloud-controller-manager/issues/14#issuecomment-762111511 and it was suggested that a separate issue will be opened for it.