Hello,
Could you try changing the image to squashtest/squash-orchestrator:4.9 (or use the tag "latest" if you prefer)?
Best regards,
Kasia
Automated Test Excution not shown on Squash TM
-
- Messages : 10
- Inscription : lun. août 21, 2023 12:05 pm
Re: Automated Test Excution not shown on Squash TM
Thank you for your idea, but I am using latest version..
sudo docker run -d --name orchestrator --link=robotenv -p 7774:7774 -p 7775:7775 -p 38368:38368 -e SSH_CHANNEL_HOST=robotenv -e SSH_CHANNEL_USER=otf -e SSH_CHANNEL_PASSWORD=siicret -e SSH_CHANNEL_TAGS=ssh,linux,robotframework -e SSH_CHANNEL_PORT=22 -e DEBUG_LEVEL=DEBUG -v /home/ubuntu/data/trusted_key.pub:/etc/squashtf/trusted_key.pub -e CURL_CA_BUNDLE=/etc/v4931_sc_fi.crt -v /usr/local/share/ca-certificates/v4931_sc_fi.crt:/etc/v4931sc_fi.crt -v /home/ubuntu/opentf-config.yaml:/app/opentf-config.yaml opentestfactory/allinone:latest
Should I try older versions? Some how execution of test case is working fine and results are visible?
So I expect Squash TM should see those results also? Now I am bit lost because there is no any error messages in logs so I cannot progress anymore?
Squash TM Test automation execution dialog is idling until I close it.
Any ideas ?
br,
NarsuMan
sudo docker run -d --name orchestrator --link=robotenv -p 7774:7774 -p 7775:7775 -p 38368:38368 -e SSH_CHANNEL_HOST=robotenv -e SSH_CHANNEL_USER=otf -e SSH_CHANNEL_PASSWORD=siicret -e SSH_CHANNEL_TAGS=ssh,linux,robotframework -e SSH_CHANNEL_PORT=22 -e DEBUG_LEVEL=DEBUG -v /home/ubuntu/data/trusted_key.pub:/etc/squashtf/trusted_key.pub -e CURL_CA_BUNDLE=/etc/v4931_sc_fi.crt -v /usr/local/share/ca-certificates/v4931_sc_fi.crt:/etc/v4931sc_fi.crt -v /home/ubuntu/opentf-config.yaml:/app/opentf-config.yaml opentestfactory/allinone:latest
Should I try older versions? Some how execution of test case is working fine and results are visible?
So I expect Squash TM should see those results also? Now I am bit lost because there is no any error messages in logs so I cannot progress anymore?
Squash TM Test automation execution dialog is idling until I close it.
Any ideas ?
br,
NarsuMan
Re: Automated Test Excution not shown on Squash TM
YES! YES! THANK YOU!
I now got it working! Your feedback gave me an idea to recheck used docker image,
Reason was that I was using open test factory image instead of Squash TM own version
I tried to use opentestfactory/allinone:latest but without any progress..
Now I pulled new version from https://hub.docker.com/r/squashtest/squash-orchestrator
Now I can see progress bar and result of test case is updated according result of test execution...
There is still some issues, but now I got through the fence
BR,
NarsuMan
I now got it working! Your feedback gave me an idea to recheck used docker image,
Reason was that I was using open test factory image instead of Squash TM own version
I tried to use opentestfactory/allinone:latest but without any progress..
Now I pulled new version from https://hub.docker.com/r/squashtest/squash-orchestrator
Now I can see progress bar and result of test case is updated according result of test execution...
There is still some issues, but now I got through the fence
BR,
NarsuMan
Re: Automated Test Excution not shown on Squash TM
Still some issues to fix
There is problem when orchestrator tries to send results back to Squash TM server:
ERROR in tm_executionlogpublisher: Internal error while dispatching execution log: HTTPSConnectionPool(host='v931.jpas.fi', port=443): Max retries exceeded with url: /squash/api/rest/latest/resultpublisher/402881898e189046018e2d1684e40030/automated-executions/allureReport (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1002)')))
Is there any ideas? I can connect https from container level, but does "execution log publisher"-compnent need own environment variables for certificates?
I have self signed cert so this is a main reason for problems..
There is problem when orchestrator tries to send results back to Squash TM server:
ERROR in tm_executionlogpublisher: Internal error while dispatching execution log: HTTPSConnectionPool(host='v931.jpas.fi', port=443): Max retries exceeded with url: /squash/api/rest/latest/resultpublisher/402881898e189046018e2d1684e40030/automated-executions/allureReport (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1002)')))
Is there any ideas? I can connect https from container level, but does "execution log publisher"-compnent need own environment variables for certificates?
I have self signed cert so this is a main reason for problems..
-
- Messages : 10
- Inscription : lun. août 21, 2023 12:05 pm
Re: Automated Test Excution not shown on Squash TM
Hi, NarsuMan,
You've got a typo in your certificate declaration (consult the photo in the attachment). Does this solve your problem?
We did not manage to reproduce your issue.
Best regards,
Kasia
You've got a typo in your certificate declaration (consult the photo in the attachment). Does this solve your problem?
We did not manage to reproduce your issue.
Best regards,
Kasia
- Pièces jointes
-
- certificate-declaration-error.png (34.7 Kio) Consulté 257 fois
Re: Automated Test Excution not shown on Squash TM
Hi!
Thanks for comments I "encrypted" little bit my certificate names so there is no problem with them, but I noticed that tm_executionlogpublisher cannot trust my certificates. Curl/Wget are working fine..
Because of this python specific problem I tried to locate which is default path for certificates when you are using python requests library.
I run command below inside squash orchestrator container:
python -c "import ssl; print(ssl.get_default_verify_paths())"
So I appended my Squash TM Servers cert.pem to /usr/lib/ssl/cert.pem
Now I got report uploaded in Squash TM!
BR,
NarsuMan
Thanks for comments I "encrypted" little bit my certificate names so there is no problem with them, but I noticed that tm_executionlogpublisher cannot trust my certificates. Curl/Wget are working fine..
Because of this python specific problem I tried to locate which is default path for certificates when you are using python requests library.
I run command below inside squash orchestrator container:
python -c "import ssl; print(ssl.get_default_verify_paths())"
So I appended my Squash TM Servers cert.pem to /usr/lib/ssl/cert.pem
Now I got report uploaded in Squash TM!
BR,
NarsuMan