Comment 9 for bug 1596594

Okay, so this is a very tricky one. I'm setting it back to incomplete as there still doesn't appear to be a reproducible way of triggering the issue. i.e. it may be packaging, or a sequence of packaging, or a sequence of charm upgrades, or sequence of openstack upgrades, or something else?

Drew, et al, what did you do to mitigate the situation; i.e. how did you recover it? I'm wondering whether we can put a check in and bail before it is attempted and/or putting a known issue in the release notes on how to handle the situation. Thanks very much!