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

Test Execution with Client ID rasses to error

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Test execution via ALM Client GUI runs ok. Test execution via Jenkins (using User and Password) runs ok. Test execution via jenkins using SSO runs raisses an error.

      After Jenkins finished with error there is no new run created in ALM.

      Error example from Jenkins Log File (full Log see Attachment):
      Test: [1]TC001_1487_RestAPI_Glass_7H, Id: 439649, Execution status: Running
      Test: [1]TC001_1487_RestAPI_Glass_7H, Id: 439649, Execution status: Unknown, Message: Ausnahmefehler des Servers
      Test: [1]TC001_1487_RestAPI_Glass_7H, Id: 439649, Execution status: Error, Message: No available hosts
      Test: [1]TC061_2856_RestAPI_HSR_7H, Id: 439654, Execution status: Unknown, Message: Ausnahmefehler des Servers
      Test: [1]TC061_2856_RestAPI_HSR_7H, Id: 439654, Execution status: Error, Message: No available hosts

        Attachments

        1. Enable_CSE_V1.png
          Enable_CSE_V1.png
          16 kB
        2. jenkinsLog.txt
          364 kB
        3. props26102021112003263.txt
          0.5 kB
        4. TestRunScheduler1.JPG
          TestRunScheduler1.JPG
          41 kB
        5. TestRunScheduler2.JPG
          TestRunScheduler2.JPG
          36 kB

          Activity

          Hide
          hildaboth Hilda added a comment -

          Hello,

          As I see from the configuration, the run mode is set to "Run on planned host".

          Have you checked from the ALM, from the Lab Resources,  if the Host, that is specified for the tests from ALM is available and operational?

          If the "Planned Host name" is set correctly from ALM, are you able to run the test set from ALM, without getting "No available hosts" error?

          Show
          hildaboth Hilda added a comment - Hello, As I see from the configuration, the run mode is set to "Run on planned host". Have you checked from the ALM, from the Lab Resources,  if the Host, that is specified for the tests from ALM is available and operational? If the "Planned Host name" is set correctly from ALM, are you able to run the test set from ALM, without getting "No available hosts" error?
          Hide
          emelknk Emel Konuk added a comment -

          Hi,

          yes we checked the Host and the Host name in ALM is correct. When we start a test execution from ALM it is possible to run the tests on this Host without any error like "No available hosts". 

          Show
          emelknk Emel Konuk added a comment - Hi, yes we checked the Host and the Host name in ALM is correct. When we start a test execution from ALM it is possible to run the tests on this Host without any error like "No available hosts". 
          Hide
          emelknk Emel Konuk added a comment -

          Hi,

          there is one more important information. If we use the username and password for ALM authentiation the tests will be run without any problems. When we use for the same test a SSO Authentication (API Key) we get the specified error. 

          Show
          emelknk Emel Konuk added a comment - Hi, there is one more important information. If we use the username and password for ALM authentiation the tests will be run without any problems. When we use for the same test a SSO Authentication (API Key) we get the specified error. 
          Hide
          dorin7bogdan Dorin Bogdan added a comment -

          Hi Emel Konuk,

          According to the UFT User_Guide:
          Depending on the authentication type required by your ALM server, credentials can be a username and password OR an API key for SSO authentication.

          In order to use ClientID/ApiKey credentials, please make sure the ALM server has SSO enabled and configured properly.

          For details please check ALM Setup-SSO-15.5-15.5.1.

          If the issue still persists, please propose a date / time for a meeting online, preferably between 8 AM - 4 PM UTC time.

          Show
          dorin7bogdan Dorin Bogdan added a comment - Hi Emel Konuk , According to the UFT User_Guide: Depending on the authentication type required by your ALM server, credentials can be a username and password OR an API key for SSO authentication. In order to use ClientID/ApiKey credentials, please make sure the ALM server has SSO enabled and configured properly. For details please check ALM Setup-SSO-15.5-15.5.1 . If the issue still persists, please propose a date / time for a meeting online, preferably between 8 AM - 4 PM UTC time.
          Hide
          232899 Carsten Langenhan added a comment -

          We don't wanna use SSO (by the way, I don't understand, why this add-on uses the term SSO, because it's only a logon via API Key which is not a SSO).

          If we start the tests with User (wich is 221001) and Password (saved in Jenkins) then all runs fine. If we use API Key instead, we got the described error. The API key is attached to the user (221001). So we do not understand, why the result is different, because the actions(s) are the same after the successfully log on (via User, Pwd or API key).

          We have checked all prerequesits via this documentation: https://admhelp.microfocus.com/uft/en/2021/UFT_Help/Content/User_Guide/Jenkins.htm

          Show
          232899 Carsten Langenhan added a comment - We don't wanna use SSO (by the way, I don't understand, why this add-on uses the term SSO, because it's only a logon via API Key which is not a SSO). If we start the tests with User (wich is 221001) and Password (saved in Jenkins) then all runs fine. If we use API Key instead, we got the described error. The API key is attached to the user (221001). So we do not understand, why the result is different, because the actions(s) are the same after the successfully log on (via User, Pwd or API key). We have checked all prerequesits via this documentation:  https://admhelp.microfocus.com/uft/en/2021/UFT_Help/Content/User_Guide/Jenkins.htm
          Hide
          hildaboth Hilda added a comment - - edited

          Hello,

          I suggest to open a CPE for further investigations and schedule a meeting to better understand the issue.

          https://www.microfocus.com/en-us/support/

          https://support.microfocus.com/contact/swgrp.html

           

           

          Show
          hildaboth Hilda added a comment - - edited Hello, I suggest to open a CPE for further investigations and schedule a meeting to better understand the issue. https://www.microfocus.com/en-us/support/ https://support.microfocus.com/contact/swgrp.html    
          Hide
          emelknk Emel Konuk added a comment -

          Hi,

          after our call and mail the problem is solved. We can close the Ticket.

          Thank you for your support.

          Best regards,

          Emel 

          Show
          emelknk Emel Konuk added a comment - Hi, after our call and mail the problem is solved. We can close the Ticket. Thank you for your support. Best regards, Emel 
          Hide
          dbogdan7 Dorin Bogdan added a comment -

          The issue was solved by setting the site parameter “ENABLE_CSE_V1” to ”Y” from ALM Site Administrator:

           

          Show
          dbogdan7 Dorin Bogdan added a comment - The issue was solved by setting the site parameter “ENABLE_CSE_V1” to ”Y” from ALM Site Administrator:  

            People

            Assignee:
            dbogdan7 Dorin Bogdan
            Reporter:
            emelknk Emel Konuk
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: