Comment 3 for bug 1500613

With 1.24.6, we are observing increased false test failures in OpenStack charm testing due to this lock issue.

Unfortunately, we are not in a position to easily do juju lock file checking and cleanup with the way we run tests. Each test run is 5 to 7 or more [bootstrap/deploy/test/destroy] iterations, back-to-back, run by the Amulet (and juju test) runners.

FWIW - Only one user, from one machine, regarding one deployment, is ever interacting with any given juju environment at any given time, and we still hit this issue.

WARNING configstore lock held, lock dir: /var/lib/jenkins/.juju/environments/env.lock
WARNING lock holder message: pid: 12576, operation: writing
ERROR Unable to connect to environment "osci-sv02".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
cannot read info: lock timeout exceeded