juju status: relation name oscillates for peer relations

Bug #1598897 reported by Christian Muirhead
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Christian Muirhead

Bug Description

If you deploy postgresql and run `juju status --format yaml`, two relations are listed for the application:

    relations:
      coordinator:
      - postgresql
      replication:
      - postgresql

But if you just run `juju status` you only see one relation:

RELATION PROVIDES CONSUMES TYPE
replication postgresql postgresql peer

Running `watch juju status` shows that the name shown switches between "replication" and "coordinator" randomly.

summary: - juju status relations that only differ by name collapsed in tabular
- output
+ juju status: relation name oscillates for peer relations
description: updated
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Playing around with relations a bit more it seems right that the coordinator/replication relation should be collapsed down to one, it matches how we treat non-peer ones like python-django:pgsql - postgresql:db In that case the relations just need to be sorted by relation name as well so they come back in a consistent order even when the from and to names are the same.

Revision history for this message
Christian Muirhead (2-xtian) wrote :
Changed in juju-core:
status: New → In Progress
importance: Undecided → High
milestone: none → 2.0-beta12
assignee: nobody → Christian Muirhead (2-xtian)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta12 → none
milestone: none → 2.0-beta12
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.