Deploying a bundle with application matching existing subordinate application fails
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
New
|
Undecided
|
Unassigned | ||
Bug Description
Deploying a bundle which defines a subordinate application - i.e. an application with no placement information or constraints in the bundle, to a model where that application already exists, attempts to reference placement data which does not exist in the model or the bundle.
This results in the deployment of a bundle to an existing model to fail when subordinate applications are defined in the bundle -
Error messages such as this are seen in the debug log:
ERROR cannot deploy bundle: getting application constraints: unable to get constraints for "filebeat": constraints do not apply to subordinate applications
This can be reproduced with a bundle stanza such as -
filebeat:
charm: "cs:xenial/
Deploying this bundle twice should show the above error, whereas with the new code to be able to deploy on top of existing models, this should be a non operation.
| Andrew McLeod (admcleod) wrote | #1 |
Confirmed with juju version 2.3.1-xenial-s390x