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

Rundeck - Could not find a job with the identifier

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rundeck-plugin

      Hello,

      As you can see in the screenshot "error.jpg" (cf. attachment), I cannot use the job's reference to identify a job in rundeck plugin.

      When I use the UUID, Jenkins display this message :
      Your Rundeck job is : b06a976e-beba-411b-add7-190df590dee9 [RE7] SYSTEM/SCAN_BUNDLES --> all is ok with UUID.

      If I am connected on Rundeck with the same account used with the Rundeck plugin on Jenkins, when access to this URL on my browser :

      http://lrundeck1:8080/rundeck/api/11/jobs?project=RE7

      I can see in the XML response my job and all others job of my project RE7 :
      <job id="b06a976e-beba-411b-add7-190df590dee9"><name>SCAN_BUNDLES</name><group>SYSTEM</group><project>RE7</project><description>This job should be used to register a new bundle into Rundeck.
      NB: only last 20 uploaded bundles are registered on Rundeck.</description></job>

      Do you know why I cannot identify my job with the reference RE7:SYSTEM/SCAN_BUNDLES? And why it works only with UUID or ID?

      Feel free to ask me if you need more informations.

      Thx in advance.
      Regards

          [JENKINS-27892] Rundeck - Could not find a job with the identifier

          Greg Schueler added a comment -

          searching for a job using project and name will only work if you have a single job with that same group and name in the project. Make sure you don't have more than one job with the same exact name and group

          Greg Schueler added a comment - searching for a job using project and name will only work if you have a single job with that same group and name in the project. Make sure you don't have more than one job with the same exact name and group

          Kevin Defives added a comment -

          Hello Greg,
          I don't have more than one job with the same exact name and group but I still have the problem.

          When I called this URL from my browser : http://rundeck-server/rundeck/api/11/jobs?project=RE7&group=SYSTEM
          I have this response :

          <jobs count="10">
          ...

          <job id="b06a976e-beba-411b-add7-190df590dee9">
          <name>SCAN_BUNDLES</name>
          <group>SYSTEM</group>
          <project>RE7</project>
          <description>This job should be used to register a new bundle into Rundeck.
          NB: only last 20 uploaded bundles are registered on Rundeck.</description>
          </job>
          ...
          </jobs>

          As you can see, the job exists and it is not a duplicated job.

          Can you help me?
          Thanks in advance.

          Regards

          Kevin Defives added a comment - Hello Greg, I don't have more than one job with the same exact name and group but I still have the problem. When I called this URL from my browser : http://rundeck-server/rundeck/api/11/jobs?project=RE7&group=SYSTEM I have this response : <jobs count="10"> ... <job id="b06a976e-beba-411b-add7-190df590dee9"> <name>SCAN_BUNDLES</name> <group>SYSTEM</group> <project>RE7</project> <description>This job should be used to register a new bundle into Rundeck. NB: only last 20 uploaded bundles are registered on Rundeck.</description> </job> ... </jobs> As you can see, the job exists and it is not a duplicated job. Can you help me? Thanks in advance. Regards

          Evan Powell added a comment -

          I have this issue on v3.5.1 as well. My Jenkins jobs are simple freestyle jobs, and the Rundeck jobs are all in uniquely named groups (job names are not unique however).

          I have a suspicion that it may have to do with Jenkins' authenticated session with Rundeck expiring. Occasionally, my Jenkins job that triggers and tails a Rundeck job execution will fail with the error message "Rundeck is not running !". This occurs even when I am interacting with Rundeck directly in another tab.

          Our session expiration setting on Rundeck is 30 minutes. We're updating it to 12 hours, but if my theory is correct this will only mitigate the issue and not solve it.

          Evan Powell added a comment - I have this issue on v3.5.1 as well. My Jenkins jobs are simple freestyle jobs, and the Rundeck jobs are all in uniquely named groups (job names are not unique however). I have a suspicion that it may have to do with Jenkins' authenticated session with Rundeck expiring. Occasionally, my Jenkins job that triggers and tails a Rundeck job execution will fail with the error message "Rundeck is not running !". This occurs even when I am interacting with Rundeck directly in another tab. Our session expiration setting on Rundeck is 30 minutes. We're updating it to 12 hours, but if my theory is correct this will only mitigate the issue and not solve it.

            vbehar Vincent Behar
            kevin_dfv Kevin Defives
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: