Subordinate charm deployment ignores global series settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
Problem statement:
When deploying a subordinate charm, it simply ignores a series explicitly being set in bundle (and machine of primary charm, as well). I have a locally stored bundle [1], and while deploying it, I'm getting a following error while trying to establish a relation:
ERROR cannot deploy bundle: cannot add relation between "nova-compute:
(full log: https:/
It looks like Juju ignores an original series of primary charm and takes just first one from subordinate's metadata [2]; if I manually swap a "xenial" with "bionic" in metadata, redeploy a subordinate and try to establish relation - all is fine: [3] (also, if try to deploy Xenial machines - all is fine too, this reproduces on Bionic machines)
Expected behaviour:
Subordinate charm should take its series from primary machine series, or, at least, respect a bundle "series: ..." settings.
[1] https:/
[2] https:/
[3] https:/
Environment:
Juju macOS 2.4.3-mojave-amd64 (same on Ubuntu 2.4.3-bionic-amd64)
Controller: https:/
description: | updated |
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I think the bug here is that the subordinate, when resolving what series to use, should be respecting the bundle default ahead of it's own preference in the multi-series list. Since this is a local charm I think it's skipping some of that normal logic.