The problem was first seen with a deployment of cs:postgresql, where the network-get failed. The diagnosis several minutes later with 'juju run' showed relation-ids reporting the dead relation, which is what caused the charm to run network-get on the dead relation (because it was told it still existed).
The problem was first seen with a deployment of cs:postgresql, where the network-get failed. The diagnosis several minutes later with 'juju run' showed relation-ids reporting the dead relation, which is what caused the charm to run network-get on the dead relation (because it was told it still existed).