bundles don't deploy applications with resources as a single step
Bug #1883036 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
As discussed here
https:/
deploying a bundle will set up the application in the juju model and then set resources as a separate step, even though everything is defined together in the bundle.
This has the effect of incrementing (possibly multiple times) the charm modified counter for the app and causes upgrade-charm hooks to be run unnecessarily on initial deployment.
Changed in juju: | |
milestone: | 2.8-next → 2.9.1 |
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Changed in juju: | |
milestone: | 2.9.3 → 3.0.0 |
Changed in juju: | |
milestone: | 3.0.0 → 3.0.1 |
Changed in juju: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in juju: | |
milestone: | 3.0.2 → 3.0.3 |
To post a comment you must log in.
Would this be clearer as "bundles don't deploy applications with resources as a single step" ? Because there is also the atomic nature of adding all the relations, multiple applications, etc.
I think the more we can do the better, but it seems like scoping this down to just "when deploying an application include the resources at the same time" would be more appropriate.