Deploying a bundle with caas charm specific setting doesn't work on subsequent deploy

[Benjamin Allot]

Hello,

I've crafted a very simple bundle.yaml file with my new k8s charm:

bundle: kubernetes
applications:
  mm-pd-bot:
    charm: cs:~mm-pd-bot-charmers/mm-pd-bot
    scale: 1
    options:
      image_path: stg-is.docker-registry.canonical.com/mm-pd-bot:v1
      mm_pd_bot_cfg: include-file://{{ local_dir }}/bot.cfg
      tls_secret_name: mm-pd-bot-staging-canonical-com-tls
      # Those parameters are k8s specific
      juju-external-hostname: mm-pd-bot.staging.canonical.com

As you can see, I use a caas specific attribute for the ingress, "juju-external-hostname"

When I deploy the first time, all is well.

However, any subsequent run fails like this : https://pastebin.canonical.com/p/mJVFzn7Cs9/

[Achilleas Anagnostopoulos (achilleasa)]

PR https://github.com/juju/juju/pull/11912 includes a fix for 2.8

[Achilleas Anagnostopoulos (achilleasa)]

PR https://github.com/juju/juju/pull/11916 supersedes the previous fix proposal.