relation output in juju status is ambiguous
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
High
|
Unassigned | ||
Bug Description
on juju status only one of the two relation names is listed
[Relations]
SERVICE1 SERVICE2 RELATION TYPE
haproxy haproxy peer peer
haproxy review-queue website regular
postgresql postgresql replication peer
postgresql review-queue db regular
rabbitmq-server rabbitmq-server cluster peer
rabbitmq-server review-queue amqp regular
http://
In this case, postgresql review-queue is actually postgresql:db-admin postgresql:db I'd like to propose the following, since relation name is unique to service and not global.
[Relations]
SERVICE1 SERVICE2 TYPE
haproxy haproxy peer
haproxy:
postgresql postgresql peer
postgresql:db-admin review-queue:db regular
rabbitmq-server rabbitmq-server peer
rabbitmq-
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0-beta7 |
| tags: | added: juju-release-support status |
| tags: | added: usability |
| Changed in juju-core: | |
| milestone: | 2.0-beta7 → 2.0-beta8 |
| Changed in juju-core: | |
| milestone: | 2.0-beta8 → 2.0-rc1 |
| Changed in juju-core: | |
| milestone: | 2.0-rc1 → 2.0.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
| Alexis Bruemmer (alexis-bruemmer) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Invalid |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
The format for relations status has changed and this bug is no longer valid. Marco, please reopen with updated feedback if you would like additional changes to relation status information.