When a conversion request has been sent to a remote master, that remote master fails, and the sender becomes the new master of the resource, the requested lkb needs to be moved from the converting queue back to the granted queue prior to processing the conversion request locally.
When a conversion request has been sent to a remote master, that
remote master fails, and the sender becomes the new master of the
resource, the requested lkb needs to be moved from the converting
queue back to the granted queue prior to processing the conversion
request locally.

Previously, we were leaving the lkb on the converting queue.  The
specific problem I observed from this happened when the conversion
was NOQUEUE and returned -EAGAIN.  When an unlock for the lkb
happened later on, dlm_unlock would find an incorrect status in the
lkb of CONVERTING, return an error and trigger an assertion failure.

asp24/resource-agents,stevenraspudic/resource-agents,stevenraspudic/resource-agents,asp24/resource-agents,asp24/resource-agents,stevenraspudic/resource-agents