Surprising charm downgrade

Bug #1574798 reported by Andreas Hasenack on 2016-04-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

I had a model with cs:trusty/haproxy-19 deployed, and proceeded to deploy a bundle that specified cs:trusty/haproxy-10 and other charms.

To my surprise, juju downgraded the haproxy charm from -19 to -10 (console output attached):

$ juju deploy ./bundles.yaml
added charm cs:trusty/haproxy-10
upgraded charm for existing service haproxy (from cs:trusty/haproxy-19 to cs:trusty/haproxy-10)
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.

Andreas Hasenack (ahasenack) wrote :
Curtis Hovey (sinzui) on 2016-04-25
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
Curtis Hovey (sinzui) on 2016-05-13
Changed in juju-core:
milestone: 2.0-beta7 → 2.0-beta8
Changed in juju-core:
milestone: 2.0-beta8 → 2.0-beta9
Curtis Hovey (sinzui) on 2016-06-16
Changed in juju-core:
milestone: 2.0-beta9 → 2.0-beta10
Curtis Hovey (sinzui) on 2016-06-24
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
Curtis Hovey (sinzui) on 2016-10-06
Changed in juju:
milestone: 2.0.0 → 2.0.1
Curtis Hovey (sinzui) on 2016-11-01
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers