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

Bug #1891524 reported by Benjamin Allot on 2020-08-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Achilleas Anagnostopoulos

Bug Description

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/

Tags: k8s Edit Tag help
Ian Booth (wallyworld) on 2020-08-18
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.8.3
tags: added: k8s
Changed in juju:
assignee: nobody → Achilleas Anagnostopoulos (achilleasa)
Changed in juju:
status: Triaged → In Progress
Ian Booth (wallyworld) on 2020-08-19
Changed in juju:
milestone: 2.8.3 → 2.8.2

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

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers