Comment 2 for bug 1803426

In order to fix this issue, we can create a device level lock, based on device_fqname to indicate the device is locked and some operation is being performed on it. So, we can also test the lock to check if the device is free of any ongoing operations and then set the lock on that device before beginning the job. This change will be part of another big change. (This change would be included as part of the job manager in DM (migrating the job manager from fabric to DM)).