cmr: remote SAAS status incorrectly reported in consuming model
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
juju: 2.5.0
ubuntu: bionic (not that this really matters).
I'm using Cross Model Relations between two models on the same controller; the service providing the relation comes up in a 'blocked' state as it knows it needs to be related to consuming services before it can consider itself active; once the offer is consumed and a relation made, the relation completes successfully and all units on both sides of the relation report active, however SAAS still reports 'blocked' on the consuming model status output:
[brundall-east]
SAAS Status Store URL
rgw-brundall-west blocked jamespage-
[brundall-west]
Unit Workload Agent Machine Public address Ports Message
...
rgw-brundall-
rgw-hacluster/0* active idle 10.5.0.13 Unit is ready and clustered
rgw-brundall-west/1 active idle 7 10.5.0.20 80/tcp Unit is ready
rgw-hacluster/1 active idle 10.5.0.20 Unit is ready and clustered
rgw-brundall-west/2 active idle 8 10.5.0.12 80/tcp Unit is ready
rgw-hacluster/2 active idle 10.5.0.12 Unit is ready and clustered
It looks like the SAAS status is not getting refreshed once the providing service switches to active status.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.2 |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.1 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 9740