Workhorse: Ignore misconfigured redis for DWS locking

Igor Drozdovrequested to merge
id-workhorse-dws-decouple-from-redis-failures into master

What does this MR do and why?

Currently, even when an error is not related to locking (for example, redis is unreachable), we fail to execute a flow: https://log.gprd.gitlab.net/app/r/s/soPkZ.

This MR takes only ErrTaken error into account and if we have a different one, we proceed without locking.

Testing

  1. Locking works as expected:
  • Start chat in one tab and open it in a separate tab
  • Chat shows that it's being execute in another tab
  1. Imitate unreachable redis: edit workhorse/config.toml to have <path>/redis/redis1.socket for example
  • gdk restart gitlab-workhorse
  • Start chat
  • gdk tail -f gitlab-workhorse has an entry that says that a lock failed to be acuired
  • Open the chat in another parallel tab - it's not locked
Edited by Igor Drozdov

Merge request reports