cert-manager: Propagation check failed, wrong service used by cm-acme-http-solver

Describe the bug: Propagation check failed, wrong service used by cm-acme-http-solver and ACME cannot check validity of the domain and deliver certificate

Expected behaviour: Challenge success and certificate delivered

Steps to reproduce the bug: Following https://docs.cert-manager.io/en/latest/tutorials/acme/http-validation.html , but I have multiple subdomains at the same time.

Anything else we need to know?: I move from cert-manager 0.8 to 0.11 few weeks. All works fine, with new subdomains added. Since few days, new subdomains failed to be validated.

Environment details::

• Kubernetes version : v1.13.10
• Cloud-provider : Azure AKS
• cert-manager version : v0.11.0
• Install method : helm

/kind bug

kubectl describe challenge:

Name:         tls-secret-1495667673-716095195-908999738
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  acme.cert-manager.io/v1alpha2
Kind:         Challenge
Metadata:
  Creation Timestamp:  2019-11-20T10:00:11Z
  Finalizers:
    finalizer.acme.cert-manager.io
  Generation:  1
  Owner References:
    API Version:           cert-manager.io/v1alpha2
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Order
    Name:                  tls-secret-1495667673-716095195
    UID:                   81e087b8-0b7c-11ea-95a0-7e8b3f31c3c5
  Resource Version:        10962589
  Self Link:               /apis/acme.cert-manager.io/v1alpha2/namespaces/default/challenges/tls-secret-1495667673-716095195-908999738
  UID:                     8a97cf77-0b7c-11ea-95a0-7e8b3f31c3c5
Spec:
  Authz URL:  https://acme-v02.api.letsencrypt.org/acme/authz-v3/1322577887
  Dns Name:   domain20.convertigo.net
  Issuer Ref:
    Group:  cert-manager.io
    Kind:   Issuer
    Name:   letsencrypt-prod
  Key:      BZiefIaNveMd0bwXbjywYExT6wGHdETnJLs5D6iZOAY.zIJBhOqgURIGfuNbqfatmAXt5je_GyTDV34tQ02Xqmw
  Solver:
    Http 01:
      Ingress:
        Class:  nginx
  Token:        BZiefIaNveMd0bwXbjywYExT6wGHdETnJLs5D6iZOAY
  Type:         http-01
  URL:          https://acme-v02.api.letsencrypt.org/acme/chall-v3/1322577887/aUEJmg
  Wildcard:     false
Status:
  Presented:   true
  Processing:  true
  Reason:      Waiting for http-01 challenge propagation: wrong status code '503', expected '200'
  State:       pending
Events:        <none>

I have a cm-acme-http-solver-wmpps Ingress with:

  "spec": {
    "rules": [
      {
        "host": "domain20.convertigo.net",
        "http": {
          "paths": [
            {
              "path": "/.well-known/acme-challenge/BZiefIaNveMd0bwXbjywYExT6wGHdETnJLs5D6iZOAY",
              "backend": {
                "serviceName": "cm-acme-http-solver-9mddf",
                "servicePort": 8089
              }
            }
          ]
        }
      }
    ]
  },

It refers a Service cm-acme-http-solver-9mddf that don’t exist but I have a cm-acme-http-solver-6c7r2. Is this normal ?

Do you need another information or do you know a work around ?

Thx !