SovLabs Custom Naming, or other SovLabs integrations that use locks are suddenly unable to obtain a lock and provisioning is stopped.
See the bottom of this article for a list of all the SovLabs integrations that use locks and can be affected by an abandoned one.
The following error may be seen in the vRO logs.
Attempting LOCK with lock ID: 'sovlabs.generateHostname.main.lock' [E] Error in (Workflow:Custom Naming / Lock (item16)#2) Wrapped java.lang.InterruptedException: sleep interrupted
Attempting LOCK with lock ID: 'sovlabs.generateHostname.main.lock'
[E] Error in (Workflow:Custom Naming / Lock (item16)#2) Wrapped java.lang.InterruptedException: sleep interrupted
If a previous lock didn't get cleaned up due to a failure, the next workflow run will hang, waiting to obtain a new lock. This will cause provisioning of VMs whose requests include the SovLabs module in question to stop because locks cannot be obtained.
You will see the SovLabs workflow stuck on the Lock scriptable task:
Sovlabs Plugin v2019.8 and older
Workaround or Solution
If this happens, you can run the Force Unlock - Hostname Generation workflow to clear the abandoned lock. Restarting vRO will not clear a lock.
If that doesn't clear it, you can run the workflows to Display all locks and Release all locks.
If you're experiencing a hung up SovLabs workflow due to a lock on something other than Custom Naming, see the list of Manual unlock workflows for other SovLabs modules below:
- Snapshot Management
- SovLabs IPAM
- Veeam (Baas)
- BlueCat DNS
- VM Tagging
- Ansible Tower (Remove hosts)