Now certificate issue fixed. No progress...
About my setup: (ip changed)
Squash TM VM in own public ip: 123.123.123.123
Orchestrator VM in own public ip: 125.12.23.23 running as container (172.17.0.3)
Robot Framework runner in docker inside Orchestrator
I did some debug with container lever.. I am little bit lost? Is there problem with orchestrator who cannot find Squash TM??
So I assume there is some problem with DSN in container level?
I added message sequence diagram about steps during test automation execution
.. and some frames
![dns querys.png](./download/file.php?id=1500&sid=562f3da1165661a6436d9317e5831318)
- dns querys.png (53.94 Kio) Consulté 196 fois
I have also executed Now open-otf client from other virtual machine and it seems workflow is executed correctly:
WORKFLOW_ID STATUS NAME
f74d45fa-5d96-456c-bae1-e5df010a299e DONE Workflow for Squash TM test suite: Tukko V1.1 > CAMP1 > ITE1 > Automation 1
ubuntu@squash-tm-2:/home$ opentf-ctl get workflow f74d45fa-5d96-456c-bae1-e5df010a299e
Workflow Workflow for Squash TM test suite: Tukko V1.1 > CAMP1 > ITE1 > Automation 1
(running in namespace 'default')
[2024-03-11T08:52:23] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Requesting execution environment providing ['robotframework'] in namespace 'default' for job 'squashTMJob-0'
[2024-03-11T08:52:23] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function actionscheckoutv2
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Cloning into 'presta-shop-tests'...
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] warning: redirecting to
https://gitlab.branet.jk.fi/shared/pres ... tests.git/
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function robotframeworkparamsv1
[2024-03-11T08:52:25] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function robotframeworkexecutev1
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 244 Standard account creation :: Fixing not running test case
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Standard account creation
| PASS |
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ------------------------------------------------------------------------------
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 244 Standard account creation :: Fixing not running test case | PASS |
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 1 test, 1 passed, 0 failed
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Output: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/output.xml
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Log: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/log.html
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Report: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/report.html
[2024-03-11T08:52:50] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:52:51] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:52:51] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:53:00] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Releasing execution environment for job 'squashTMJob-0'
Workflow completed successfully.
It seems that problem is at Squash TM side? Why progress bar is not actively updating? If Workflow is accessible by client (at other vm) there should be no problem at orchestrator side? I cannot see any error messages about connection timeout etc...
BR,
NarsuMan