Duplicate file mounts in CaaS charm causes silent failure
Bug #1854104 reported by
Kenneth Koski
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.
Changed in juju: | |
milestone: | none → 2.7.1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.7.1 → 2.7.2 |
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 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.