Why in queue: Strict security prevents tasks without an owning item from executing

Article ID:360041020472
1 minute readKnowledge base

Issue

Jobs waiting in the queue with the message (when moused over): Why in queue: Strict security prevents tasks without an owning item from executing and not making progress

Resolution

When seeing the message: Why in queue: Strict security prevents tasks without an owning item from executing the issue is caused by JENKINS - 53837 and has been fixed in version 2.24 of the Pipeline: Nodes and Processes plugin.

Suggested Steps:

  • Back-up $JENKINS_HOME directory

  • Upgrade Pipeline: Nodes and Processes plugin to version 2.24 or later

  • Execute a test job assigned to a specific agent to verify the problem was solved.

References