Comment 1 for bug 1915466

A few possible ways to address this:

- See if it's feasible for the charm to clean up the lock if an update or deployment fails (not sure we can be aware of all the failure modes and whether this is feasible though).
- Make sure if this lock does exist there's an easy mechanism to communicate that to charm operators (possibly we should set the charm to blocked status).
- Give operators an easy way to remove it, possibly via a charm action, and make it obvious that that's how to do it.

I think having a lock expiry is potentially dangerous because we're playing a guessing game as to how long that should be. Set it too low or too high and there are downsides. I'd be open to being convinced otherwise, but that's my initial instinct here.