Comment 5 for bug 1979981

While the error is different from bug #1975726 it could be a different code path with the same root cause. (how we were interacting with resources that had been updated was wrong prior to 2.9.32)
If there is a rush to get this working again, that is likely the most expedient path. We haven't been able to reproduce the original failure yet to confirm that we think the 2.9.31 bug was common (the original bug doesn't reproduce unless you trigger a refresh from charmhub, which doesn't naturally happen for 24hrs.)