Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16538

Resource remains sporadically locked

    Details

    • Similar Issues:

      Description

      The resource remains sporadically locked in spite of a successful release on log

      Collecting metadata...
      Metadata collection done.
      Releasing previously locked resource: 0019001200190071...
      Resource 0019001200190071 successfully released.
      Finished: SUCCESS

      Possibly the root cause can be the same as JENKINS-16302

        Attachments

          Issue Links

            Activity

            Hide
            debeerstb Benjamin Debeerst added a comment -

            I can confirm that this also happens to me. Is there a workaround? How do I manually unlock a resource?

            Show
            debeerstb Benjamin Debeerst added a comment - I can confirm that this also happens to me. Is there a workaround? How do I manually unlock a resource?
            Hide
            debeerstb Benjamin Debeerst added a comment -

            I have found out that a manual "unlock" can be performed by changing the resource's metadata.

            Furthermore, my log output shows the following:

            Metadata collection done.
            Releasing previously locked resource: ...
            WARNING The resource has already been unlocked by some other means. The Build might have suffered from it.
            Finished: SUCCESS

            So this might be another issue. Any suggestions?

            Show
            debeerstb Benjamin Debeerst added a comment - I have found out that a manual "unlock" can be performed by changing the resource's metadata. Furthermore, my log output shows the following: Metadata collection done. Releasing previously locked resource: ... WARNING The resource has already been unlocked by some other means. The Build might have suffered from it. Finished: SUCCESS So this might be another issue. Any suggestions?
            Hide
            debeerstb Benjamin Debeerst added a comment - - edited

            Ok, the problem could be solved when I specified IDs for each of the resources. I had only specified names. This should be checked by the plugin though, thus I created JENKINS-17556.

            Show
            debeerstb Benjamin Debeerst added a comment - - edited Ok, the problem could be solved when I specified IDs for each of the resources. I had only specified names. This should be checked by the plugin though, thus I created JENKINS-17556 .
            Hide
            maxrossello Massimo Rossello added a comment -

            I found that simply re-saving unmodified node configuration unlocks the resource (I have IDs defined, if that matters).

            Then, I have to kill the job which thought to have the resource locked, but didn't proceed further for some reason, otherwise it remains in queue forever

            Show
            maxrossello Massimo Rossello added a comment - I found that simply re-saving unmodified node configuration unlocks the resource (I have IDs defined, if that matters). Then, I have to kill the job which thought to have the resource locked, but didn't proceed further for some reason, otherwise it remains in queue forever

              People

              • Assignee:
                rsandell rsandell
                Reporter:
                maxrossello Massimo Rossello
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: