Receiving an Access Denied error when trying to run ALM tests from Jenkins

  • Questions
  • DevOps
  • Receiving an Access Denied error when trying to run ALM tests from Jenkins
Category:
Question ID: 109758
1
1

Hello. I am getting access denied from the ALM execution on Jenkins.

We resolved the issue by logging onto the controlling remote desktop, but I receive the following with Jenkins.

—————————

11:39:34 Test: [1]CheckServerStatus, Status: Unknown, Message: Test run stopped. [host: MACHINEAUTO5], Link: td://alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

11:39:35 Test: [1]Flow OpenFloat, Status: Error, Message: Access is denied,

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

11:39:35 Test: [2]Flow OpenFloat, Status: Error, Message: Access is denied,

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=-1

11:39:35 Test: [3]Flow OpenFloat, Status: Passed, Message: Test run passed. [host: MACHINEAUTO3],

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

11:39:35 Test: [4]Flow OpenFloat, Status: Error, Message: Access is denied,

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

11:39:35 Test: [6]Flow OpenFloat, Status: Error, Message: Access is denied,

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

11:39:35 Test: [7]Flow OpenFloat, Status: Unknown, Message: Test run stopped. [host: MACHINEAUTO5],

Link: td:// alm.company.prod:8080/qcbin//TestRunsModule-000000000?EntityType=IRun&EntityID=00000

Marked as spam
Posted by (Questions: 217, Answers: 21)
Asked on July 31, 2020 12:44 pm
6 views
Answers (1)
1
Private answer

Hello. I have found where this issue can occur when the user running the test in ALM is not the same as the one configured in Jenkins. You may also want to make sure that the user running the test is in a user group within ALM that has adequate permissions to run the affected tests. Try running the Jenkins service using Admin credentials, and retest to see if the issue still occurs.

Marked as spam
Posted by (Questions: 2, Answers: 278)
Answered on July 31, 2020 12:45 pm