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

'Run could not start' error from HPE Application Automation Tools plugin

    Details

    • Similar Issues:

      Description

      Following on from JENKINS-52366, the version of the automation tools plugin from that bug has an issue when running a build job. This is the Jenkins log;

      Fri 07.20.2018 at 11:21:44 AM BST - 
      Run started (TestID: 1764, RunID: 1905, TimeslotID: 4001)

      Fri 07.20.2018 at 11:21:48 AM BST - Error: executeRequest exception: Operation failed. Error code: 1001
      Fri 07.20.2018 at 11:21:48 AM BST - Error: Run could not start!
      Fri 07.20.2018 at 11:21:49 AM BST - Logout succeeded
      Fri 07.20.2018 at 11:21:49 AM BST - Empty Results
      Fri 07.20.2018 at 11:21:49 AM BST - Result Status (PC RunID: 1905): FAILURE

       

      Checking the corresponding test in Performance Center showed that it was triggered correctly, the test continues to run and passes successfully. The run information from Performance Center shows the following;

       

      Test Name hello_world
      Run ID 1905
      End time 07/20/2018 11:22:02

       

      This was broken during the fix for 52366, I was able to run a successful job on the 17th of July but it had stopped working by the 20th. The bug log suggest the change for DecimalFormatSymbols whitelisting broke the build job. 

        Attachments

          Activity

          Hide
          umesh6023 Umesh Gachinmath added a comment -

          Hi Daniel,

          No luck for me, still I am facing same issue. Few points I just wanted to notify here :

          1) Our Performance Center (PC) is hosted in different location and secured network.

          2) In order to access that PC hosted in secured network, I have to use Check-Point VPN

          Is this secured network is causing the problem ?

          Regards

          Umesh 

          Show
          umesh6023 Umesh Gachinmath added a comment - Hi Daniel, No luck for me, still I am facing same issue. Few points I just wanted to notify here : 1) Our Performance Center (PC) is hosted in different location and secured network. 2) In order to access that PC hosted in secured network, I have to use Check-Point VPN Is this secured network is causing the problem ? Regards Umesh 
          Hide
          simon_norris Simon Norris added a comment -

          Looks like I appear to have taken a step backwards, I now cannot run any tests. The job shows;

           

          Started by user unknown or anonymous
          Building in workspace C:\Jenkins_Home\workspace\get_quote_IF_proxy
          Thu 07.26.2018 at 02:45:55 PM BST - plugin version is '5.4.3-beta-SNAPSHOT'
          Thu 07.26.2018 at 02:45:55 PM BST - Validating parameters before run
          Thu 07.26.2018 at 02:45:55 PM BST - OK
          Thu 07.26.2018 at 02:45:55 PM BST - Trying to login
          [PCServer='http://bob', User='me.too']
          Thu 07.26.2018 at 02:45:56 PM BST - Login succeeded
          Thu 07.26.2018 at 02:45:56 PM BST - Searching for available Test Instance
          Thu 07.26.2018 at 02:45:56 PM BST - Found testInstanceId: 378
          Thu 07.26.2018 at 02:46:01 PM BST - Error: executeRequest exception: Operation failed. Error code: 1001
          Thu 07.26.2018 at 02:46:01 PM BST - Error: Run could not start!
          Thu 07.26.2018 at 02:46:02 PM BST - Logout succeeded
          Thu 07.26.2018 at 02:46:02 PM BST - Empty Results
          Thu 07.26.2018 at 02:46:02 PM BST - Result Status: FAILURE

           

          And the error log shows even less;

          Jul 26, 2018 2:46:03 PM hudson.model.Run execute
          INFO: get_quote_IF_proxy #10 main build action completed: FAILURE

           

          The only difference I can think of is a new Jenkins.war file, I'm currently on 2.121.2

           

          Show
          simon_norris Simon Norris added a comment - Looks like I appear to have taken a step backwards, I now cannot run any tests. The job shows;   Started by user unknown or anonymous Building in workspace C:\Jenkins_Home\workspace\get_quote_IF_proxy Thu 07.26.2018 at 02:45:55 PM BST - plugin version is '5.4.3-beta-SNAPSHOT' Thu 07.26.2018 at 02:45:55 PM BST - Validating parameters before run Thu 07.26.2018 at 02:45:55 PM BST - OK Thu 07.26.2018 at 02:45:55 PM BST - Trying to login [PCServer='http://bob', User='me.too'] Thu 07.26.2018 at 02:45:56 PM BST - Login succeeded Thu 07.26.2018 at 02:45:56 PM BST - Searching for available Test Instance Thu 07.26.2018 at 02:45:56 PM BST - Found testInstanceId: 378 Thu 07.26.2018 at 02:46:01 PM BST - Error: executeRequest exception: Operation failed. Error code: 1001 Thu 07.26.2018 at 02:46:01 PM BST - Error: Run could not start! Thu 07.26.2018 at 02:46:02 PM BST - Logout succeeded Thu 07.26.2018 at 02:46:02 PM BST - Empty Results Thu 07.26.2018 at 02:46:02 PM BST - Result Status: FAILURE   And the error log shows even less; Jul 26, 2018 2:46:03 PM hudson.model.Run execute INFO: get_quote_IF_proxy #10 main build action completed: FAILURE   The only difference I can think of is a new Jenkins.war file, I'm currently on 2.121.2  
          Hide
          simon_norris Simon Norris added a comment - - edited

          I am able to trigger the same test from a PC REST API request.

          I did notice that the REST request needed a TestInstanceID, whereas the plugin is set to Automatically select. However, setting the plugin TestInstanceId to manual and giving it a number didn't make any difference.

          Show
          simon_norris Simon Norris added a comment - - edited I am able to trigger the same test from a PC REST API request. I did notice that the REST request needed a TestInstanceID, whereas the plugin is set to Automatically select. However, setting the plugin TestInstanceId to manual and giving it a number didn't make any difference.
          Hide
          danieldanan Daniel Danan added a comment -

          Hi Simon, Hi Umesh,

          @Umesh, the authentication passes OK but then the first PC REST operation fails (which is getCorrectTestInstanceID). I suggest you verify if the PC user defined in Jenkins job does indeed have enough permissions on the PC project where the test is defined. As for vpn being a possible issue, I don't think so otherwise authentication would have failed (try to set a user with wrong password and you should see an authentication failure).

          @Simon, your last logs show indeed a regression as it is a situation that should be handled now. The failure occurs when trying to get the testname and with the last plugin i sent you, it is now ignored and replaced by providing run_id instead of the testname which allows the job to continue forward. I cannot say why the REST API fails to retrieve the testname (perhaps some permission issues or something else, I hope our QA can reproduce this behavior which will allow me to debug because i am not) but this name is used to create, later on, a meaningful link for reports and is not really essential for the execution of the test). Try to download once again the last plugin i uploaded to this case and use it (perhaps there was a confusion between all the plugin i uploaded in this defect report and the previous one). I don't think the version has something to do with this as i am using Jenkins 2.132 (see sreenshot).

          Regards,
          Daniel

          Show
          danieldanan Daniel Danan added a comment - Hi Simon, Hi Umesh, @Umesh, the authentication passes OK but then the first PC REST operation fails (which is getCorrectTestInstanceID). I suggest you verify if the PC user defined in Jenkins job does indeed have enough permissions on the PC project where the test is defined. As for vpn being a possible issue, I don't think so otherwise authentication would have failed (try to set a user with wrong password and you should see an authentication failure). @Simon, your last logs show indeed a regression as it is a situation that should be handled now. The failure occurs when trying to get the testname and with the last plugin i sent you, it is now ignored and replaced by providing run_id instead of the testname which allows the job to continue forward. I cannot say why the REST API fails to retrieve the testname (perhaps some permission issues or something else, I hope our QA can reproduce this behavior which will allow me to debug because i am not) but this name is used to create, later on, a meaningful link for reports and is not really essential for the execution of the test). Try to download once again the last plugin i uploaded to this case and use it (perhaps there was a confusion between all the plugin i uploaded in this defect report and the previous one). I don't think the version has something to do with this as i am using Jenkins 2.132 (see sreenshot). Regards, Daniel
          Hide
          danieldanan Daniel Danan added a comment -

          Hi,
          Please let me know if you continue facing troubles with this fix.
          Just for you to know, a new plugin is now released in Jenkins Plugins marketplace and it takes into considerations the JEP-200 problems. Feel free to download it from there.
          regards,
          Daniel

          Show
          danieldanan Daniel Danan added a comment - Hi, Please let me know if you continue facing troubles with this fix. Just for you to know, a new plugin is now released in Jenkins Plugins marketplace and it takes into considerations the JEP-200 problems. Feel free to download it from there. regards, Daniel

            People

            • Assignee:
              danieldanan Daniel Danan
              Reporter:
              simon_norris Simon Norris
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: