aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Isaac Councill <>
Subject one lock to lock them all
Date Wed, 10 Sep 2014 18:03:55 GMT

I just experienced an issue where a job update was failing and leaving a
lock in place. Expected. What I didn't expect was that while that lock was
in place, it was not possible to interact with any job (old or new) due to
the lock. All the jobs I tested were in the same role and prod environment.

Is this behavior intentional?

I'm working with the 0.5.0-incubating release.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message