Duplicate file mounts in CaaS charm causes silent failure

Bug #1854104 reported by Kenneth Koski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Yang Kelvin Liu

Bug Description

I've got a charm that creates a pod with two containers in it. Each one has a `files` section wherein I added a mount named `certs`. The operator pod successfully calls pod-spec-set, and shows no errors, but the workload pod never gets created. Renaming one of the mounts to e.g. `certs2` makes the deployment work fine. I'm assuming this is due to the Kubernetes YAML that's generating having a volume name conflict of some sort, but can't verify due to not being able to find any actual errors, just a silent failure to create the pod.

Tags: k8s
Revision history for this message
Kenneth Koski (knkski) wrote :

As an example, I've got a no-longer-relevant charm that demonstrates the issue here:

https://github.com/juju-solutions/bundle-kubeflow/blob/adding-istio-bundle/charms/istio-telemetry/reactive/charm.py

Note that both containers have an `istio-certs` file mount.

Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.7.1
importance: Undecided → High
status: New → Triaged
Changed in juju:
milestone: 2.7.1 → 2.7.2
Ian Booth (wallyworld)
tags: added: k8s
Changed in juju:
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
status: Triaged → In Progress
Changed in juju:
milestone: 2.7.2 → 2.7.3
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

https://github.com/juju/juju/pull/11232 will land into 2.8 to fix this

Changed in juju:
milestone: 2.7.3 → 2.8-beta1
Changed in juju:
status: In Progress → Fix Committed
Harry Pidcock (hpidcock)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.