Comment 1 for bug 1871898

Revision history for this message
Ian Booth (wallyworld) wrote : Re: [2.7.5] Stale CMR offers causing model to not destroy properly

It's interesting that the cross model relations join ok but won't get removed. That fact that they join ok suggests it's not an issue with communication between controllers.

It would be interesting to see if --force applied to remove-saas and/or destroy-model and/or remove-relation causes cleanup to complete. The --force option will eventually cleanup the model on which it is run even if the other side is not responding.

Before doing that though, we need more info to diagnose the issue. We need logs fpr both models and their controller controller, after turning on extra debug logging on both models:

juju model-config logging-config="juju.apiserver.common.crossmodel=DEBUG;juju.apiserver.crossmodelrelations=DEBUG;juju.worker.uniter.remotestate=DEBUG;<root>=INFO;UNIT=DEBUG;"

Turn on the logging, set up and deployment, and then remove relation etc. We need to see what cmr related events get published between the models to understand why things are getting stuck.