Surprising charm downgrade
Bug #1574798 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
I had a model with cs:trusty/
To my surprise, juju downgraded the haproxy charm from -19 to -10 (console output attached):
$ juju deploy ./bundles.yaml
added charm cs:trusty/
upgraded charm for existing service haproxy (from cs:trusty/
configuration updated for service haproxy
(...)
I think juju should loudly complain about this situation, maybe even refuse to deploy. But not downgrade a charm just like that.
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
| tags: | added: upgrade-charm |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: bundles juju-release-support |
| Changed in juju-core: | |
| milestone: | none → 2.0-beta7 |
| tags: | added: usability |
| Changed in juju-core: | |
| milestone: | 2.0-beta7 → 2.0-beta8 |
| Changed in juju-core: | |
| milestone: | 2.0-beta8 → 2.0-beta9 |
| Changed in juju-core: | |
| milestone: | 2.0-beta9 → 2.0-beta10 |
| Changed in juju-core: | |
| milestone: | 2.0-beta10 → 2.0-beta11 |
| Changed in juju-core: | |
| importance: | High → Medium |
| milestone: | 2.0-beta11 → none |
| Changed in juju-core: | |
| milestone: | none → 2.0.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.