juju upgrade-charm errors when it shouldn't
Bug #1510787 reported by
Tim Penhey
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
postgresql (Juju Charms Collection) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I have an environment with cs:trusty/
I wanted to upgrade it to the latest, which is now cs:trusty/
Unfortunately Juju said "no".
cs:trusty/
peers:
replication:
interface: pgreplication
and cs:trusty/
peers:
replication:
interface: pgpeer
I have just one unit of postgresql, and since it is a peer relation, it is automatically related to itself. The charm upgrade code notices that the interface changes, and stops the upgrade.
Juju should allow this upgrade, even if it is only when there is one unit.
Changed in juju-core: | |
milestone: | 1.26-alpha1 → 1.26-alpha2 |
Changed in juju-core: | |
milestone: | 1.26-alpha2 → 1.26.0 |
Changed in juju-core: | |
milestone: | 1.26.0 → 2.0-beta1 |
Changed in juju-core: | |
milestone: | 2.0-beta1 → 2.0-beta2 |
Changed in juju-core: | |
milestone: | 2.0-beta2 → 2.0-beta3 |
Changed in juju-core: | |
milestone: | 2.0-beta3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.1 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.1 → none |
milestone: | none → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 1.25.10 |
Changed in juju: | |
milestone: | none → 2.2.0 |
Changed in juju-core: | |
milestone: | 1.25.10 → none |
Changed in juju-core: | |
milestone: | none → 1.25.11 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
ERROR cannot upgrade service "postgresql" to charm "local: trusty/ postgresql- 1": would break relation "postgresql: replication"
Alas, the interface name cannot be changed back without breaking even more deployments.
People trying to upgrade from the old PostgreSQL charm will need to branch the PostgreSQL charm, edit metadata.yaml changing 'interface: pgpeer' to 'interface: pgreplication', and upgrade to this branch. This will become unnecessary after upgrading to a version of juju-core with the fix.