Comment 23 for bug 1735402

The most recent work that is going into 2.5 has been to detect that a cloud credential that a model uses has become invalid, i.e. cloud rejects calls with auth errors, and to stop communicating with the cloud until the credential is changed.

This should minimise the amount of logging that is happening on the model with an invalid credential -most of the logging was related to a model making and failing a cloud call.

In addition to allowing model and controller administrators to update cloud credential as per existing process described in this bug, Juju 2.5 allows to replace model credential to a different credential, see 'set-credential' help for more details.

The fact that a cloud credential has become invalid is discoverable too - there are additional stanzas in 'show-model' command as well as the commands to 'show-credential <name>' [shows specified credential] and 'show-credentials' [shows all credentials stored on the controller for the currently logged on user].

I am closing this bug as 'Fix Committed' and targeting 2.5 milestone.