Config automatisation Squash Orchestrator

GambettaLimonade
Messages : 9
Inscription : mer. avr. 16, 2025 12:11 am

Config automatisation Squash Orchestrator

Message par GambettaLimonade »

Bonjour,
J'ai des cas de tests écrit en .robot qui sont sur un gitlab. J'ai essayé de configuré squashTM et squash Orchestrator pour pouvoir lancer mes scripts auto .robot directement depuis l'interface squashTM, cependant je recontre des difficultés. Voilà ce que j'ai set up :

dans la partie cas de test :

- j'ai déclaré mes cas de tests comme étant éligible à l'auto, et j'ai renseigné les champs comme suit :
Technologie du test auto. Robot Framework
URL du dépôt de code source https://gitlab.com/IssamMerikhi/OrangeHRM.git (main)
Référence du test auto. OrangeHRM/test_gitlabCICD.robot

dans la partie administration :

- j'ai déclaré un worflow d'automatisation à squash avancé
- j'ai déclarer un jeton d'API de lecture et d'écriture à mon admin (moi même)
- le serveur d'execution automatisé
- le serveur de partage de code source
- j'ai installé l'orchestrator via les commandes

Code : Tout sélectionner

docker pull squashtest/squash-orchestrator:latest
et

Code : Tout sélectionner

docker run -d \
         --name orchestrator \
         -p 7774:7774 \
         -p 7775:7775 \
         -p 7776:7776 \
         -p 38368:38368 \
         -e SSH_CHANNEL_HOST=the_environment_ip_or_hostname \
         -e SSH_CHANNEL_USER=user \
         -e SSH_CHANNEL_PASSWORD=secret \
         -e SSH_CHANNEL_TAGS=ssh,linux,robotframework \
          squashtest/squash-orchestrator:latest
quand je vais dans les logs docker voilà ce que j'obtiens :

2025-04-16 00:04:38.928 | [2025-04-15 22:04:38,927] INFO in startup: No license was provided, Premium Interpreter will not be launched.
2025-04-16 00:04:38.928 | [2025-04-15 22:04:38,928] INFO in startup: Reading OpenTestFactory Launcher Manifest 'squashtf.yaml' ...
2025-04-16 00:04:38.931 | [2025-04-15 22:04:38,931] INFO in startup: Image name: squash-orchestrator
2025-04-16 00:04:38.931 | [2025-04-15 22:04:38,931] INFO in startup: Image build date: 2025-03-05 15:32:15.442008
2025-04-16 00:04:38.931 | [2025-04-15 22:04:38,931] INFO in startup: Base image: allinone (version: 2025-02.00)
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,934] INFO in startup: OpenTestFactory orchestrator version: 0.69.0
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,935] INFO in startup: OpenTestFactory python-toolkit version: 0.61.0
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: Environment variables:
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: CURL_CA_BUNDLE not set. No default value.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: DEBUG not set. Using default value: 'INFO'.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: DEBUG_LEVEL not set. Using default value: 'INFO'.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: HTTP_PROXY not set. No default value.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: HTTPS_PROXY not set. No default value.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: KEY_SIZE not set. Using default value: 4096.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: NO_PROXY not set. No default value.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_TELEMETRY not set. No default value.
2025-04-16 00:04:38.948 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_ALLURE_ENABLED not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_AUTHORIZATION_MODE not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_AUTHORIZATION_POLICY_FILE not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_BASE_URL not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_CONTEXT not set. Using default value: 'allinone'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_DEBUG not set. Using default value: 'INFO'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_EVENTBUS_WARMUPDELAY not set. Using default value: 2.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_EVENTBUS_WARMUPURL not set. Using default value: 'http://127.0.0.1:38368/subscriptions'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_EVENTBUSCONFIG not set. Using default value: 'conf/eventbus.yaml'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_HEALTHCHECK_DELAY not set. Using default value: 60.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_LAUNCHERMANIFEST: '8c84a10f-d433-48cb-b5ae-213a7aadcda2.yaml'
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_PLUGINDESCRIPTOR not set. Using default value: 'plugin.yaml'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_SERVICEDESCRIPTOR not set. Using default value: 'service.yaml'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,936] INFO in startup: OPENTF_TOKEN_AUTH_FILE not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: OPENTF_TRUSTEDKEYS_AUTH_FILE not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: OPENTF_TRUSTEDKEYS_PATHS not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: PUBLIC_EXP not set. Using default value: 65537.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: PUBLIC_KEY not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: PYTHONPATH not set. No default value.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: TRUSTED_KEYS_FILE not set. Using default value: 'trusted_key.pub'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: TRUSTEDKEYS_PATH not set. Using default value: '/etc/squashtf'.
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: SQUASH_LICENSE_TYPE: 'community'
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,937] INFO in startup: Reading OpenTestFactory Launcher Manifest '8c84a10f-d433-48cb-b5ae-213a7aadcda2.yaml' ...
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,938] INFO in startup: Checking Configuration...
2025-04-16 00:04:38.949 | [2025-04-15 22:04:38,938] INFO in startup: Creating temporary JWT token
2025-04-16 00:04:39.543 | [2025-04-15 22:04:39,543] INFO in startup: eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzcXVhc2ggb3JjaGVzdHJhdG9yIiwic3ViIjoidGVtcCB0b2tlbiJ9.TkiWXry8yb1GFlO0hQN8Itc1vvjEYmHg0lmMwCPyZ3PIcQ6zF5jKT_Uc5i4t-fWILYx8WYM1nEqvAGz_j1wsKfWCGSJXDzPFvxew19tR3Sbri3VjfU3WSosZpbaCyvr0OuIppcAsB_WvTi1q2T1pUQTbxQShPgsuyx5Z5wqmeT1fbAsxh6wfvlpWyqP9xoGZESJfXn5Y1gYepfJSRuS2nti5xRbS3uJ3BVgkqDc8LCimK9BGQZFtA-wcofFeu2vTe70u-IkzI75N0fPQD93wQDTS2QLKOd1YPgGsnNz07J7IeS9OwDmJUjmTGbdTxkXNvQZrxeFmClXBnR4VKcEceVcCpwTRo9htUvd3ZxfOOP5wsyX0jObk0HZu7EVBgBhrm-9wVTwTHlHxRrvX3-dGBSOOfPBQL46h2UcuzjEr7AOVHICUiMqpjHHp-Ff30aSSzc_Lt3dTUuTMXCaUmccmoLQ_1fGwHpGj4zJn3EAmpYwI6zhyY94G59AyIe9RAFxlTXW-MMTN1QfPegabhot-KliUYSF7PlPIh24akhaPYB3C8kmk_NXtQUkWYDIVFuOkOiN4htvC0aUQSvqcXEb0WuHzH7T4qW_wDOxmkJ0JpflyvUrp8t32CyUqFuoFkQ7PvlVuzirbxiaLgFsVy_m3e5hR-xMc5uzDkQSfg5tFaEI
2025-04-16 00:04:39.544 | [2025-04-15 22:04:39,544] INFO in startup: Checking EventBus...
2025-04-16 00:04:39.544 | [2025-04-15 22:04:39,544] INFO in startup: Starting ['python3', '-m', 'opentf.core.eventbus', '--context', 'allinone']...
2025-04-16 00:04:41.120 | [2025-04-15 22:04:41,120] INFO in eventbus: Configuration:
2025-04-16 00:04:41.121 | [2025-04-15 22:04:41,120] INFO in eventbus: publication timeout in seconds (post_timeout_seconds): 10
2025-04-16 00:04:41.150 | [2025-04-15 22:04:41,150] INFO in eventbus: Serving on http://0.0.0.0:38368
2025-04-16 00:04:41.150 | [2025-04-15 22:04:41,150] INFO in eventbus: number of threads for the waitress server (waitress_threads_count): 10
2025-04-16 00:04:41.556 | [2025-04-15 22:04:41,555] INFO in startup: Starting Core Services...
2025-04-16 00:04:41.559 | [2025-04-15 22:04:41,559] INFO in startup: Starting ['python3', '-m', 'opentf.core.receptionist', '--context', 'allinone']...
2025-04-16 00:04:41.568 | [2025-04-15 22:04:41,568] INFO in startup: Starting ['python3', '-m', 'opentf.core.arranger', '--context', 'allinone']...
2025-04-16 00:04:41.571 | [2025-04-15 22:04:41,571] INFO in startup: Starting ['python3', '-m', 'opentf.core.observer', '--context', 'allinone']...
2025-04-16 00:04:41.572 | [2025-04-15 22:04:41,572] INFO in startup: Starting ['python3', '-m', 'opentf.core.killswitch', '--context', 'allinone']...
2025-04-16 00:04:41.575 | [2025-04-15 22:04:41,574] INFO in startup: Starting ['python3', '-m', 'opentf.core.localstore', '--context', 'allinone']...
2025-04-16 00:04:43.524 | [2025-04-15 22:04:43,524] INFO in killswitch: Serving on http://0.0.0.0:7776
2025-04-16 00:04:43.525 | [2025-04-15 22:04:43,524] INFO in killswitch: Configuration:
2025-04-16 00:04:43.525 | [2025-04-15 22:04:43,524] INFO in killswitch: waitress_threads_count: 4
2025-04-16 00:04:43.553 | [2025-04-15 22:04:43,552] INFO in receptionist: Serving on http://0.0.0.0:7774
2025-04-16 00:04:43.553 | [2025-04-15 22:04:43,552] INFO in receptionist: Configuration:
2025-04-16 00:04:43.553 | [2025-04-15 22:04:43,553] INFO in receptionist: waitress_threads_count: 4
2025-04-16 00:04:43.560 | [2025-04-15 22:04:43,560] INFO in localstore: Serving on http://0.0.0.0:34537
2025-04-16 00:04:43.560 | [2025-04-15 22:04:43,560] INFO in localstore: Configuration:
2025-04-16 00:04:43.560 | [2025-04-15 22:04:43,560] INFO in localstore: waitress_threads_count: 4
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,561] INFO in arranger: Configuration:
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: maximum number of jobs per workflow (max_jobs): 1024
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: maximum number of simultaneously running jobs (max_parallel): 1
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: maximum number of steps per job (max_job_steps): 10240
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: maximum number of workers per workflow (max_workers): 4
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: default job timeout in minutes (default_timeout_minutes): 360
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: additional environment tags for uses-type jobs workflow downloads (download_job_tags):
2025-04-16 00:04:43.562 | [2025-04-15 22:04:43,562] INFO in arranger: use or ignore uses-type jobs environment tags (download_job_parents_tags): use
2025-04-16 00:04:43.584 | [2025-04-15 22:04:43,583] INFO in observer: Configuration:
2025-04-16 00:04:43.584 | [2025-04-15 22:04:43,583] INFO in observer: maximum workflow retention count (max_retention_workflow_count): 0
2025-04-16 00:04:43.584 | [2025-04-15 22:04:43,584] INFO in observer: maximum workflow retention period in minutes (max_retention_period_minutes): 0
2025-04-16 00:04:43.584 | [2025-04-15 22:04:43,584] INFO in observer: workflow retention period in minutes (retention_period_minutes): 60
2025-04-16 00:04:43.618 | [2025-04-15 22:04:43,618] INFO in arranger: Serving on http://127.0.0.1:7781
2025-04-16 00:04:43.618 | [2025-04-15 22:04:43,618] INFO in arranger: waitress_threads_count: 4
2025-04-16 00:04:43.655 | [2025-04-15 22:04:43,655] INFO in observer: Serving on http://0.0.0.0:7775
2025-04-16 00:04:43.655 | [2025-04-15 22:04:43,655] INFO in observer: number of threads for the waitress server (waitress_threads_count): 10
2025-04-16 00:04:45.598 | [2025-04-15 22:04:45,597] INFO in startup: Starting Plugins...
2025-04-16 00:04:45.639 | [2025-04-15 22:04:45,639] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.rewriter.main', '--context', 'allinone']...
2025-04-16 00:04:45.643 | [2025-04-15 22:04:45,643] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.inceptionee.main', '--context', 'allinone']...
2025-04-16 00:04:45.695 | [2025-04-15 22:04:45,695] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.trackerpublisher.main', '--context', 'allinone']...
2025-04-16 00:04:45.744 | [2025-04-15 22:04:45,743] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.agentchannel.main', '--context', 'allinone']...
2025-04-16 00:04:45.785 | [2025-04-15 22:04:45,785] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.insightcollector.main', '--context', 'allinone']...
2025-04-16 00:04:45.812 | [2025-04-15 22:04:45,812] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.sshee.main', '--context', 'allinone']...
2025-04-16 00:04:45.820 | [2025-04-15 22:04:45,815] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.allinone.main', '--context', 'allinone']...
2025-04-16 00:04:45.834 | [2025-04-15 22:04:45,832] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.qualitygate.main', '--context', 'allinone']...
2025-04-16 00:04:45.854 | [2025-04-15 22:04:45,846] INFO in startup: Starting ['python3', '-m', 'opentf.plugins.s3publisher.main', '--context', 'allinone']...
2025-04-16 00:04:45.863 | [2025-04-15 22:04:45,862] INFO in startup: Starting ['python3', '-m', 'squash.retryer.main', '--context', 'allinone']...
2025-04-16 00:04:45.870 | [2025-04-15 22:04:45,869] INFO in startup: Starting ['/app/tm-connector/scripts/launch_scripts/generator.sh', '--context', 'allinone']...
2025-04-16 00:04:45.877 | [2025-04-15 22:04:45,872] INFO in startup: Starting ['python3', '-m', 'squash.logpublisher.main', '--context', 'allinone']...
2025-04-16 00:04:45.877 | [2025-04-15 22:04:45,874] INFO in startup: Starting ['/app/tm-connector/scripts/launch_scripts/launch_micronaut_service.sh', 'tm-publisher-${TM_CONNECTOR_VERSION}.tar.gz', 'tm-publisher-${TM_CONNECTOR_VERSION}/squash-tm-publisher-native-image', '--context', 'allinone']...
2025-04-16 00:04:45.883 | [2025-04-15 22:04:45,882] INFO in startup: Starting ['/bin/bash', '/app/plugins/interpreter/launch_interpreter.sh', '--context', 'allinone']...
2025-04-16 00:04:45.961 | [2025-04-15 22:04:45,959] INFO in startup: OpenTestFactory Orchestrator Ready.
2025-04-16 00:04:45.961 | [2025-04-15 22:04:45,960] INFO in startup: Started eventbus.
2025-04-16 00:04:45.961 | [2025-04-15 22:04:45,960] INFO in startup: Started 5 core services.
2025-04-16 00:04:45.961 | [2025-04-15 22:04:45,960] INFO in startup: Started 14 plugins.
2025-04-16 00:04:47.830 | __ __ _ _
2025-04-16 00:04:47.830 | | \/ (_) ___ _ __ ___ _ __ __ _ _ _| |_
2025-04-16 00:04:47.830 | | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|
2025-04-16 00:04:47.830 | | | | | | (__| | | (_) | | | | (_| | |_| | |_
2025-04-16 00:04:47.830 | |_| |_|_|\___|_| \___/|_| |_|\__,_|\__,_|\__|
2025-04-16 00:04:47.872 | [2025-04-15 22:04:47,872] INFO in tm.generator.community: Setting log level 'INFO' for logger: 'org.squashtest'
2025-04-16 00:04:47.872 | [2025-04-15 22:04:47,872] INFO in tm.generator.community: Setting log level 'INFO' for logger: 'org.opentestfactory'
2025-04-16 00:04:47.961 | [2025-04-15 22:04:47,961] INFO in tm.generator.community: GeneratorCommand endpoint will be http://127.0.0.1:10065/generator/inbox
2025-04-16 00:04:47.961 | [2025-04-15 22:04:47,961] INFO in tm.generator.community: Event bus generatorCommandSubscription 'tm.generator' registered as '4ecb44e6-ad6b-4ee3-88ac-fe6ef58b1dbf'
2025-04-16 00:04:47.965 | [2025-04-15 22:04:47,965] INFO in tm.generator.community: SuiteDefinitionReceipt endpoint will be http://127.0.0.1:10065/generator/inbox/suiteReceipt
2025-04-16 00:04:47.965 | [2025-04-15 22:04:47,965] INFO in tm.generator.community: Event bus suiteDefinitionReceiptSubscription 'tm.generator' registered as 'fa3b9f05-8bd1-4655-a034-99db70b91cae'
2025-04-16 00:04:47.965 | [2025-04-15 22:04:47,965] INFO in tm.generator.community: Startup completed in 136ms. Server Running: http://06435ee1eefb:10065
2025-04-16 00:04:48.180 | __ __ _ _
2025-04-16 00:04:48.180 | | \/ (_) ___ _ __ ___ _ __ __ _ _ _| |_
2025-04-16 00:04:48.180 | | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|
2025-04-16 00:04:48.180 | | | | | | (__| | | (_) | | | | (_| | |_| | |_
2025-04-16 00:04:48.180 | |_| |_|_|\___|_| \___/|_| |_|\__,_|\__,_|\__|
2025-04-16 00:04:48.244 | [2025-04-15 22:04:48,244] INFO in tm.publisher: Setting log level 'INFO' for logger: 'org.squashtest'
2025-04-16 00:04:48.245 | [2025-04-15 22:04:48,245] INFO in tm.publisher: Setting log level 'INFO' for logger: 'org.opentestfactory'
2025-04-16 00:04:48.315 | [2025-04-15 22:04:48,314] INFO in inceptionee: Providing environments for the following tags: {'inception'}.
2025-04-16 00:04:48.330 | [2025-04-15 22:04:48,325] INFO in tm.publisher: ExpectedSuiteDefinition endpoint will be http://127.0.0.1:10066/publisher/inbox/suiteDefinition
2025-04-16 00:04:48.330 | [2025-04-15 22:04:48,325] INFO in tm.publisher: Event bus suiteDefinitionSubscription 'tm.publisher' registered as '20680c8f-6207-48a2-86b7-a621742e6dd5'
2025-04-16 00:04:48.339 | [2025-04-15 22:04:48,338] INFO in tm.publisher: ExecutionResult endpoint will be http://127.0.0.1:10066/publisher/inbox/executionResult
2025-04-16 00:04:48.339 | [2025-04-15 22:04:48,339] INFO in tm.publisher: Event bus executionResultSubscription 'tm.publisher' registered as '3bb81e95-8539-4aab-9020-70834c5429c5'
2025-04-16 00:04:48.358 | [2025-04-15 22:04:48,356] INFO in tm.publisher: ReportInterpreterOutput endpoint will be http://127.0.0.1:10066/publisher/inbox/ ... eterOutput
2025-04-16 00:04:48.358 | [2025-04-15 22:04:48,356] INFO in tm.publisher: Event bus interpreterOutputSubscription 'tm.publisher' registered as '7673b51a-5159-4a24-9a71-61b298034a8a'
2025-04-16 00:04:48.367 | [2025-04-15 22:04:48,360] INFO in tm.publisher: WorkflowCancellation endpoint will be http://127.0.0.1:10066/publisher/inbox/ ... ncellation
2025-04-16 00:04:48.367 | [2025-04-15 22:04:48,361] INFO in tm.publisher: Event bus WorkflowCancellationSubscription 'tm.publisher' registered as 'fee1ad4e-f82a-4f6b-8957-0ed652daeafd'
2025-04-16 00:04:48.388 | [2025-04-15 22:04:48,380] INFO in tm.publisher: WorkflowCanceled endpoint will be http://127.0.0.1:10066/publisher/inbox/workflowCancel
2025-04-16 00:04:48.388 | [2025-04-15 22:04:48,380] INFO in tm.publisher: Event bus workflowCanceledSubscription 'tm.publisher' registered as '8adc8394-7a76-47d8-9a25-e17ce9c6e719'
2025-04-16 00:04:48.388 | [2025-04-15 22:04:48,381] INFO in tm.publisher: Startup completed in 201ms. Server Running: http://06435ee1eefb:10066
2025-04-16 00:04:48.417 | [2025-04-15 22:04:48,417] INFO in inceptionee: Serving on http://127.0.0.1:7791
2025-04-16 00:04:48.418 | [2025-04-15 22:04:48,418] INFO in inceptionee: Configuration:
2025-04-16 00:04:48.420 | [2025-04-15 22:04:48,419] INFO in inceptionee: waitress_threads_count: 4
2025-04-16 00:04:48.489 | 22:04:48,485 |-INFO in ch.qos.logback.classic.LoggerContext[default] - This is logback-classic version 1.4.11
2025-04-16 00:04:48.489 | 22:04:48,485 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - No custom configurators were discovered as a service.
2025-04-16 00:04:48.489 | 22:04:48,485 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - Trying to configure with ch.qos.logback.classic.joran.SerializedModelConfigurator
2025-04-16 00:04:48.489 | 22:04:48,485 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - Constructed configurator of type class ch.qos.logback.classic.joran.SerializedModelConfigurator
2025-04-16 00:04:48.489 | 22:04:48,485 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.scmo]
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.scmo]
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - ch.qos.logback.classic.joran.SerializedModelConfigurator.configure() call lasted 1 milliseconds. ExecutionStatus=INVOKE_NEXT_IF_ANY
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - Trying to configure with ch.qos.logback.classic.util.DefaultJoranConfigurator
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - Constructed configurator of type class ch.qos.logback.classic.util.DefaultJoranConfigurator
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [resource:/logback.xml]
2025-04-16 00:04:48.489 | 22:04:48,486 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@43bce7d6 - Resource [logback.xml] occurs multiple times on the classpath.
2025-04-16 00:04:48.489 | 22:04:48,486 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@43bce7d6 - Resource [logback.xml] occurs at [resource:/logback.xml#1]
2025-04-16 00:04:48.489 | 22:04:48,486 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@43bce7d6 - Resource [logback.xml] occurs at [resource:/logback.xml]
2025-04-16 00:04:48.489 | 22:04:48,486 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@20fe89d3 - URL [resource:/logback.xml] is not of type file
2025-04-16 00:04:48.489 | 22:04:48,487 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [STDOUT]
2025-04-16 00:04:48.489 | 22:04:48,487 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [STDOUT] to Logger[ROOT]
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@715ca840 - End of configuration.
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@7a847745 - Registering current configuration as safe fallback point
2025-04-16 00:04:48.489 | 22:04:48,488 |-INFO in ch.qos.logback.classic.util.ContextInitializer@5d23c75d - ch.qos.logback.classic.util.DefaultJoranConfigurator.configure() call lasted 2 milliseconds. ExecutionStatus=DO_NOT_INVOKE_NEXT_IF_ANY
2025-04-16 00:04:48.489 |
2025-04-16 00:04:48.493 | __ __ _ _
2025-04-16 00:04:48.493 | | \/ (_) ___ _ __ ___ _ __ __ _ _ _| |_
2025-04-16 00:04:48.493 | | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|
2025-04-16 00:04:48.493 | | | | | | (__| | | (_) | | | | (_| | |_| | |_
2025-04-16 00:04:48.493 | |_| |_|_|\___|_| \___/|_| |_|\__,_|\__,_|\__|
2025-04-16 00:04:48.520 | [2025-04-15 22:04:48,520] INFO in interpreter: Setting log level 'INFO' for logger: 'org.opentestfactory'
2025-04-16 00:04:48.578 | [2025-04-15 22:04:48,578] INFO in interpreter: ReportInterpreterInput endpoint will be http://127.0.0.1:10093/postmanReportInterpreter/report
2025-04-16 00:04:48.587 | [2025-04-15 22:04:48,587] INFO in interpreter: Event bus reportInputSubscription 'postman.interpreter' registered as '9a889a3f-4998-4018-a5ba-2b10b2419e5f'
2025-04-16 00:04:48.588 | [2025-04-15 22:04:48,588] INFO in interpreter: ExecutionResult endpoint will be http://127.0.0.1:10093/postmanReportInterpreter/result
2025-04-16 00:04:48.593 | [2025-04-15 22:04:48,593] INFO in interpreter: Event bus executionResultSubscription 'postman.interpreter' registered as 'd1c91595-9b2c-48e6-8774-9374ae53a784'
2025-04-16 00:04:48.594 | [2025-04-15 22:04:48,594] INFO in interpreter: ReportInterpreterInput endpoint will be http://127.0.0.1:10093/robotReportInterpreter/report
2025-04-16 00:04:48.597 | [2025-04-15 22:04:48,597] INFO in interpreter: Event bus reportInputSubscription 'robotframework.interpreter' registered as '251f41b2-2e2b-415c-abcf-e59745db45b5'
2025-04-16 00:04:48.597 | [2025-04-15 22:04:48,597] INFO in interpreter: ExecutionResult endpoint will be http://127.0.0.1:10093/robotReportInterpreter/result
2025-04-16 00:04:48.602 | [2025-04-15 22:04:48,602] INFO in interpreter: Event bus executionResultSubscription 'robotframework.interpreter' registered as '943ae626-45f5-4c76-ba38-73f64376165b'
2025-04-16 00:04:48.605 | [2025-04-15 22:04:48,603] INFO in interpreter: ReportInterpreterInput endpoint will be http://127.0.0.1:10093/configurableSure ... ter/report
2025-04-16 00:04:48.606 | [2025-04-15 22:04:48,606] INFO in interpreter: Event bus reportInputSubscription 'configurableSurefire.interpreter' registered as '0d0fa09d-f7d1-484b-bd74-9bc0a3dcda91'
2025-04-16 00:04:48.607 | [2025-04-15 22:04:48,607] INFO in interpreter: ExecutionResult endpoint will be http://127.0.0.1:10093/configurableSure ... ter/result
2025-04-16 00:04:48.610 | [2025-04-15 22:04:48,610] INFO in interpreter: Event bus executionResultSubscription 'configurableSurefire.interpreter' registered as 'fbbcf3cf-3f97-4ea3-a7b6-de10a2283c4a'
2025-04-16 00:04:48.610 | [2025-04-15 22:04:48,610] INFO in interpreter: Startup completed in 117ms. Server Running: http://06435ee1eefb:10093
2025-04-16 00:04:48.633 | [2025-04-15 22:04:48,633] INFO in rewriter: Serving on http://127.0.0.1:7794
2025-04-16 00:04:48.634 | [2025-04-15 22:04:48,633] INFO in rewriter: Configuration:
2025-04-16 00:04:48.634 | [2025-04-15 22:04:48,633] INFO in rewriter: waitress_threads_count: 4
2025-04-16 00:04:48.663 | [2025-04-15 22:04:48,662] INFO in tm_executionlogpublisher: Configuration:
2025-04-16 00:04:48.663 | [2025-04-15 22:04:48,663] INFO in tm_executionlogpublisher: how long to wait before initializing execution log (execution_log_warmup_seconds): 5
2025-04-16 00:04:48.663 | [2025-04-15 22:04:48,663] INFO in tm_executionlogpublisher: how long to wait before updating execution log (execution_log_update_seconds): 300
2025-04-16 00:04:48.663 | [2025-04-15 22:04:48,663] INFO in tm_executionlogpublisher: how long to wait for workers to complete (workers_max_wait_seconds): 300
2025-04-16 00:04:48.664 | [2025-04-15 22:04:48,663] INFO in tm_executionlogpublisher: how long to wait before rechecking if workers are still busy (workers_busy_wait_seconds): 5
2025-04-16 00:04:48.664 | [2025-04-15 22:04:48,663] INFO in tm_executionlogpublisher: how long to wait after all workers have completed their work (workers_idle_grace_seconds): 10
2025-04-16 00:04:48.665 | [2025-04-15 22:04:48,665] INFO in tm_executionlogpublisher: Starting log publications dispatching thread.
2025-04-16 00:04:48.665 | [2025-04-15 22:04:48,665] INFO in tm_executionlogpublisher: Starting execution log publication thread.
2025-04-16 00:04:48.666 | [2025-04-15 22:04:48,666] INFO in tm_executionlogpublisher: Subscribing...
2025-04-16 00:04:48.685 | [2025-04-15 22:04:48,685] INFO in tm_executionlogpublisher: Starting TM Execution Log publisher service.
2025-04-16 00:04:48.692 | [2025-04-15 22:04:48,691] WARNING in trackerpublisher: No tracker instances file provided. If you want to publish results to a tracker, you must provide a list of instances in a file refered to by the TRACKERPUBLISHER_INSTANCES instance variable. The service is disabled.
2025-04-16 00:04:48.715 | [2025-04-15 22:04:48,715] INFO in agentchannel: Configuration:
2025-04-16 00:04:48.716 | [2025-04-15 22:04:48,715] INFO in agentchannel: how often to check if agents are available (availability_check_delay): 10
2025-04-16 00:04:48.716 | [2025-04-15 22:04:48,716] INFO in agentchannel: Channel handler ID: 723ebaa9-ea93-4289-a9cb-204aac33f78d.
2025-04-16 00:04:48.729 | [2025-04-15 22:04:48,729] INFO in tm_executionlogpublisher: Serving on http://127.0.0.1:7795
2025-04-16 00:04:48.730 | [2025-04-15 22:04:48,729] INFO in tm_executionlogpublisher: waitress_threads_count: 4
2025-04-16 00:04:48.734 | [2025-04-15 22:04:48,734] INFO in retryer: Starting republishing thread.
2025-04-16 00:04:48.735 | [2025-04-15 22:04:48,735] INFO in retryer: Subscribing...
2025-04-16 00:04:48.742 | [2025-04-15 22:04:48,742] INFO in trackerpublisher: Serving on http://127.0.0.1:7797
2025-04-16 00:04:48.742 | [2025-04-15 22:04:48,742] INFO in trackerpublisher: Configuration:
2025-04-16 00:04:48.742 | [2025-04-15 22:04:48,742] INFO in trackerpublisher: waitress_threads_count: 4
2025-04-16 00:04:48.763 | [2025-04-15 22:04:48,763] INFO in agentchannel: Serving on http://0.0.0.0:24368
2025-04-16 00:04:48.763 | [2025-04-15 22:04:48,763] INFO in agentchannel: number of threads for the waitress server (waitress_threads_count): 10
2025-04-16 00:04:48.768 | [2025-04-15 22:04:48,768] INFO in retryer: Starting test execution retryer plugin.
2025-04-16 00:04:48.789 | [2025-04-15 22:04:48,788] INFO in qualitygate: Configuration:
2025-04-16 00:04:48.789 | [2025-04-15 22:04:48,788] INFO in qualitygate: default scope to apply to quality gates (default_scope): test.managed==true
2025-04-16 00:04:48.789 | [2025-04-15 22:04:48,789] INFO in qualitygate: where to find quality gate definitions (definitions_path): /app/qualitygates
2025-04-16 00:04:48.791 | [2025-04-15 22:04:48,791] INFO in qualitygate: Loading default quality gate definitions and definitions from /app/qualitygates.
2025-04-16 00:04:48.815 | [2025-04-15 22:04:48,815] INFO in retryer: Serving on http://127.0.0.1:7799
2025-04-16 00:04:48.815 | [2025-04-15 22:04:48,815] INFO in retryer: Configuration:
2025-04-16 00:04:48.815 | [2025-04-15 22:04:48,815] INFO in retryer: waitress_threads_count: 4
2025-04-16 00:04:48.837 | [2025-04-15 22:04:48,837] INFO in qualitygate: Serving on http://0.0.0.0:12312
2025-04-16 00:04:48.838 | [2025-04-15 22:04:48,837] INFO in qualitygate: waitress_threads_count: 4
2025-04-16 00:04:48.848 | [2025-04-15 22:04:48,848] INFO in allinone: Aggregating the following services: actionprovider, cucumber, cypress, junit, playwright, postman, robotframework, skf, soapui.
2025-04-16 00:04:49.002 | [2025-04-15 22:04:49,001] INFO in allinone: Serving on http://127.0.0.1:17784
2025-04-16 00:04:49.002 | [2025-04-15 22:04:49,002] INFO in allinone: Configuration:
2025-04-16 00:04:49.002 | [2025-04-15 22:04:49,002] INFO in allinone: waitress_threads_count: 4
2025-04-16 00:04:49.040 | [2025-04-15 22:04:49,039] INFO in insightcollector: Configuration:
2025-04-16 00:04:49.040 | [2025-04-15 22:04:49,040] INFO in insightcollector: how long to wait for workers to complete (workers_max_wait_seconds): 30
2025-04-16 00:04:49.040 | [2025-04-15 22:04:49,040] INFO in insightcollector: default scope to use in insights (default_scope): test.managed==true
2025-04-16 00:04:49.040 | [2025-04-15 22:04:49,040] INFO in insightcollector: where to find insight configurations (configurations_path): /app/insights
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,041] INFO in sshchannel: Environment variables:
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,041] INFO in sshchannel: SSHCHANNEL_DEBUG_LEVEL not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_HOST: 'the_environment_ip_or_hostname'
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_PORT not set. Using default value: '22'.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_PASSWORD: ******
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_POOLS not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_TAGS: 'ssh,linux,robotframework'
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSH_CHANNEL_USER: 'user'
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_HOST not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_PORT not set. Using default value: '22'.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_PASSWORD not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_POOLS not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_TAGS not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: SSHCHANNEL_USER not set. No default value.
2025-04-16 00:04:49.042 | [2025-04-15 22:04:49,042] INFO in sshchannel: (If defined, SSHCHANNEL_* environment variables take precedence over SSH_CHANNEL_*)
2025-04-16 00:04:49.043 | [2025-04-15 22:04:49,043] INFO in sshchannel: Using pools: agents.
2025-04-16 00:04:49.043 | [2025-04-15 22:04:49,043] INFO in sshchannel: Configuration:
2025-04-16 00:04:49.043 | [2025-04-15 22:04:49,043] INFO in sshchannel: how often to check if agents are available (availability_check_delay): 10
2025-04-16 00:04:49.044 | [2025-04-15 22:04:49,044] WARNING in insightcollector: Duplicate insight definitions found for SurefireXmlReport "executionreport", only the definition with the highest priority will be used.
2025-04-16 00:04:49.044 | [2025-04-15 22:04:49,044] WARNING in insightcollector: Duplicate insight definitions found for SummaryReport "executionreport", only the definition with the highest priority will be used.
2025-04-16 00:04:49.045 | [2025-04-15 22:04:49,045] INFO in sshchannel: Channel handler ID: ffc0095c-176f-4429-a4fc-67c4e51560a7.
2025-04-16 00:04:49.088 | [2025-04-15 22:04:49,087] INFO in sshchannel: Serving on http://127.0.0.1:7786
2025-04-16 00:04:49.088 | [2025-04-15 22:04:49,088] INFO in sshchannel: waitress_threads_count: 4
2025-04-16 00:04:49.093 | [2025-04-15 22:04:49,092] INFO in insightcollector: Serving on http://0.0.0.0:7796
2025-04-16 00:04:49.093 | [2025-04-15 22:04:49,093] INFO in insightcollector: waitress_threads_count: 4
2025-04-16 00:04:49.237 | [2025-04-15 22:04:49,236] INFO in s3publisher: Configuration:
2025-04-16 00:04:49.237 | [2025-04-15 22:04:49,236] INFO in s3publisher: credentials location (s3credentials): /app/s3publisher/s3credentials.json
2025-04-16 00:04:49.237 | [2025-04-15 22:04:49,236] INFO in s3publisher: bucket name to put attachments on (bucket): example
2025-04-16 00:04:49.248 | [2025-04-15 22:04:49,247] WARNING in s3publisher: Missing S3 credentials /app/s3publisher/s3credentials.json.
2025-04-16 00:04:49.284 | [2025-04-15 22:04:49,283] INFO in s3publisher: Serving on http://127.0.0.1:7787
2025-04-16 00:04:49.284 | [2025-04-15 22:04:49,283] INFO in s3publisher: waitress_threads_count: 4
2025-04-16 00:04:50.067 | [2025-04-15 22:04:50,066] INFO in sshchannel: Providing environments for the following tags: ssh, linux, robotframework

donc ce que j'ai essayé de faire c'est de prendre le token fourni par le démarrage du conteneur, aller dans la partie administration et le balancé dans la partie serveur/serveur d'exécution automatisé > Politique d'authentification >Jeton ET AUSSI DANS LA PARTIE PROJETS : Environnement par défaut > Jeton.

Le soucis c'est que quand je fais ça docker me renvoie des logs invalid token comme ceci :

[2025-04-15 22:28:40,351] WARNING in receptionist: Not a known format, expecting JSON or YAML.
[2025-04-15 22:28:40,396] WARNING in killswitch: Not a valid UUID.
[2025-04-15 22:28:44,980] WARNING in receptionist: Not a known format, expecting JSON or YAML.
[2025-04-15 22:28:44,996] WARNING in killswitch: Not a valid UUID.
[2025-04-15 22:28:54,691] WARNING in receptionist: Invalid JWT token.
[2025-04-15 22:29:15,200] WARNING in receptionist: Not a known format, expecting JSON or YAML.
[2025-04-15 22:29:15,213] WARNING in killswitch: Not a valid UUID.

Qu'est ce que j'ai loupé ??... Je suis nouveau mais j'aime beaucoup la technique et je sens que je suis à pas grand chose de réussir à faire tourner le tout... Merci par avance aux âmes charitables qui m'aideront à avancer :)
Adrian
Messages : 4
Inscription : mer. nov. 15, 2023 10:42 am

Re: Config automatisation Squash Orchestrator

Message par Adrian »

Bonjour,

Je pense qu’il y a une ambiguïté concernant l’usage des tokens.

Il existe deux types de tokens utilisés dans le cadre de l’automatisation, chacun ayant un objectif différent :

- Le premier est celui associé à un profil utilisateur — dans votre cas, par exemple, à l’administrateur. Ce token donne les droits liés au profil concerné. Si je comprends bien votre message, c’est celui que vous avez créé via l’interface de Squash, dans les paramètres de votre profil.

- Le second est celui à définir au niveau de l’orchestrateur. Il est complètement distinct du token utilisateur : il sert à sécuriser la communication avec l’orchestrateur.

Vous trouverez ici un lien vers la documentation décrivant un quick start qui permet de récupérer un token généré par défaut dans l’image Docker, si aucune clé publique n’a été spécifiée :
https://opentestfactory.org/quickstart. ... chestrator

Cependant, dans un contexte de mise en production, nous recommandons fortement d’utiliser une paire de clés publique/privée.

L’idée est la suivante :

- Générer une paire de clés ;

Utiliser notre outil Python pour interagir avec l’orchestrateur, disponible ici :
https://opentestfactory.org/tools/install.html

- Exécuter la commande suivante pour générer un token sécurisé :

opentf-ctl generate token {votre_clé_privée.pem}

- Injecter ensuite la clé publique (.pub) dans l’orchestrateur pour qu’il puisse valider les tokens générés.

Voici enfin un lien vers la documentation qui détaille les différentes actions possibles ainsi que les commandes associées :
https://opentestfactory.org/installatio ... usted-keys
GambettaLimonade
Messages : 9
Inscription : mer. avr. 16, 2025 12:11 am

Re: Config automatisation Squash Orchestrator

Message par GambettaLimonade »

Bonjour Adrian,

Merci pour votre réponse !
J'avais cru comprendre qu'il y a les Jetons personnels d'API et aussi les tokens pour la connexion à l'orchestrator et j'ai vu que dans un environnement de prod il faut générer une paire de clé. Je suis sur ma machine personnelle et j'essaye justement de faire cette connexion à l'orchestrator sans générer ces clés, cependant même en lançant ses 2 commandes

Code : Tout sélectionner

docker run -d --name robotenv --env PASSWORD_ACCESS=true --env USER_NAME=otf --env USER_PASSWORD=secret opentestfactory/robot-framework-runner:latest
et

Code : Tout sélectionner

docker run -d --name orchestrator --link=robotenv -p 7774:7774 -p 7775:7775 -e SSH_CHANNEL_HOST=robotenv -e SSH_CHANNEL_USER=otf -e SSH_CHANNEL_PASSWORD=secret -e SSH_CHANNEL_TAGS=ssh,linux,robotframework -e SSH_CHANNEL_PORT=22 opentestfactory/allinone:latest
puis je récupère le token ey.... et que je le rentre dans la partie projets ET dans la partie Serveurs les 2 me renvoie un message d'erreur :

Squash n'a pas pu joindre le service 'event_bus' à l'URL 'http://0.0.0.0:38368'. (connexion refusée)

Hier j'arrivais à passer cette étape et ça me déclenchait une sous partie environnement ssh, robotframework etc... Je ne comprends pas j'ai pourtant kill le contenaire docker et réessayé 2-3 fois mais toujours pareil...

pourtant quand j'execute curl --header "Authorization: bearer eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzcXVhc2ggb3JjaGVzdHJhdG9yIiwic3ViIjoidGVtcCB0b2tlbiJ9.AYVwZnSFhffNwTaaqogqefY07eSWeX_JKc5at1TFq8uFY6zhfM7XxWDL8_miEfPWSWezPWMb9Xu_PVzJLcchucfm7neRnsPknyNg2AEQYbwWlrScXZiWEqjriK3UH9tGalaUiwHz80vs0GNBY2MnkwtAfvOqyCFaUp6_XOCfMnwKiXwlc8f9Zg9-iPnK5M3LsvlC46Y0IeRfRrgccgZjZcjAMNDqdMZ29CxoYru3p26L3hVmo5LlnsLXoHcmpVGPQDmLNjvmcfHAE3rO2Q4XSuC00evLIo1zUWJDCAtE3z6KXseor2KJzatbfI5I_OMIrJNhT1CJxwHjV9xkFpylMXHssI9BLUHka_zsmMDq7la8G8fh55-LBCnKS0z6XToICH1EszoxaphXMbkU1wl7mQG-nP0VX-Wy128EyERJp_8umS3sz8lsiVk6mytNhgAaUj54JUOTFpn7wfB2vPGkNifi-EbXmpesAqSK6i58B6FPir5GkZYiROL25QgTJ2WeINovENGFmyPFdLKikaaVgsGNSWpqxH9POS-0dqSehYsDIuMFUdLG7uE6DauKuE-2jRxgeqzMv_bmvyeg1mKFpcBRjnxkY0A9ZoNJaYE1oX0NFPgt7Bld81V-O0dnNoFg3tFT13JKhP8072BQiJ9kacPmEhJrBupEoXm0HH6HL6E" http://0.0.0.0:7775/channels

il me renvoie ça :

{"apiVersion":"v1","code":200,"details":{"items":[{"apiVersion":"opentestfactory.org/v1alpha1","kind":"Channel","metadata":{"channelhandler_id":"9a89c28a-5ed9-4b07-91a3-1e114a512f32","name":"robotenv","namespaces":"default"},"spec":{"tags":["ssh","linux","robotframework"]},"status":{"currentJobID":null,"lastCommunicationTimestamp":"2025-04-17T15:57:06.411969+00:00","phase":"IDLE"}}]},"kind":"Status","message":"Known channels","metadata":{},"reason":"OK","status":"Success"}

de ce que je comprends le token permet de joindre l'observer au moins
GambettaLimonade
Messages : 9
Inscription : mer. avr. 16, 2025 12:11 am

Re: Config automatisation Squash Orchestrator

Message par GambettaLimonade »

Re bonjour Adrian, je viens de me rendre compte que lorsque je suis la doc henix squash : https://henixdevelopment.gitlab.io/squa ... stall.html et que je lance cette commande docker :

Code : Tout sélectionner

docker run -d \
         --name orchestrator \
         -p 7774:7774 \
         -p 7775:7775 \
         -p 7776:7776 \
         -p 38368:38368 \
         -e SSH_CHANNEL_HOST=the_environment_ip_or_hostname \
         -e SSH_CHANNEL_USER=user \
         -e SSH_CHANNEL_PASSWORD=secret \
         -e SSH_CHANNEL_TAGS=ssh,linux,robotframework \
         squashtest/squash-orchestrator:latest
elle me génère un jeton que j'arrive à passer dans les sections Projets et Serveurs et donc je peux choisir un "Tags d'environnements par défaut"

par contre quand je suis la documentation opentestfactory et que je lance cette commande :

Code : Tout sélectionner

docker run -d ^
  --name orchestrator ^
  --link=robotenv ^
  -p 7774:7774 ^
  -p 7775:7775 ^
  -e SSH_CHANNEL_HOST=robotenv ^
  -e SSH_CHANNEL_USER=otf ^
  -e SSH_CHANNEL_PASSWORD=secret ^
  -e SSH_CHANNEL_TAGS=ssh,linux,robotframework ^
  -e SSH_CHANNEL_PORT=22 ^
  opentestfactory/allinone:latest
(avec la commande docker robotenv qui précède), à ce moment là, le token présent dans les logs ne passe pas dans les sections Projets et Serveurs. Est ce que ça veut dire que mon Orchestrator est correctement configuré, maintenant qu'il a un jeton valide dans Projets et Serveurs ? Je ne sais pas... Est ce qu'il y a d'autres choses à configurer ou je peux me rendre dans l'execution et essayer de lancer mes tests ??? Je ne sais pas trop...

Pour la suite des étapes je pense être un peu perdu, la finalité étant toujours la même, lancer mes scripts .robot de mon dépôt GitLab depuis l'Orchestrator

Merci pour votre aide :)
GambettaLimonade
Messages : 9
Inscription : mer. avr. 16, 2025 12:11 am

Re: Config automatisation Squash Orchestrator

Message par GambettaLimonade »

Bonjour à tous,

Je suis toujours sur mon probleme de configuration de squash Orchestrator, j'ai pu générer un token et je l'ai déclaré en variables d'env :

Code : Tout sélectionner

C:\Users\IssamMERIKHI>set TOKEN=eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzcXVhc2ggb3JjaGVzdHJhdG9yIiwic3ViIjoidGVtcCB0b2tlbiJ9.qBm4gEXo2mlSfBGoAYxq8srjSWvb5NJeJwZfqGyhAEE1VL3kyM4M6cAKjM9tuXpnc-6BEljSTmqdEQQMOk6R2g5PqzrxlHNOWdQwuNEM4RtWoPLENygQb0emM72ZOW5cHvxBct3BC2TUjHd6SUa-zSbEf3Xbkb_NE5e7GAUyV_Hd9mmpKiBWZBGBUOWRaMuZU3YtIrPmOTRzBXIRox8LBlu47-qjL2wD8L5VIwfvAqohwP8VrowCZ-Pw9DMosaag5C4D7F3DYOuN_RofuVxH069ln7blcecm5kgLGK1CtTIHYih5XfqBKUaJAwMsC8HieOjjej1SdWL6byAZqUXP-Tv_ZRg_vd8g2pLbr5J94D-KSibOvm3r3vdipij1xxgxXLTRhf1ZUdgcc65fhScQphledGJf3VK2FDz2cvIgGI-6Zk92DVsNPwCMUm-p8TutCDDrTRTFSfhgrjmZ5wspLcdlGyqYwqaZnm4BStTRKIMLhy3t0BqidF5ZDH7BwxxrZTwZyiGpd4XCkHwD7cQiz9VdmwEvJk2aMH4-0x_maIXotk3fhetPzNJtfTlloj_ygNV8wQ8mw5A9hMHGRXKF7mo49JNhXBBessMrMO2190FpaUYAtaSucs6_fMccgtn27gMcet9l-nUwiHCMP-J8aS43VmFOMfmtVmcg4xlsvWs

C:\Users\IssamMERIKHI>echo %TOKEN%
eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzcXVhc2ggb3JjaGVzdHJhdG9yIiwic3ViIjoidGVtcCB0b2tlbiJ9.qBm4gEXo2mlSfBGoAYxq8srjSWvb5NJeJwZfqGyhAEE1VL3kyM4M6cAKjM9tuXpnc-6BEljSTmqdEQQMOk6R2g5PqzrxlHNOWdQwuNEM4RtWoPLENygQb0emM72ZOW5cHvxBct3BC2TUjHd6SUa-zSbEf3Xbkb_NE5e7GAUyV_Hd9mmpKiBWZBGBUOWRaMuZU3YtIrPmOTRzBXIRox8LBlu47-qjL2wD8L5VIwfvAqohwP8VrowCZ-Pw9DMosaag5C4D7F3DYOuN_RofuVxH069ln7blcecm5kgLGK1CtTIHYih5XfqBKUaJAwMsC8HieOjjej1SdWL6byAZqUXP-Tv_ZRg_vd8g2pLbr5J94D-KSibOvm3r3vdipij1xxgxXLTRhf1ZUdgcc65fhScQphledGJf3VK2FDz2cvIgGI-6Zk92DVsNPwCMUm-p8TutCDDrTRTFSfhgrjmZ5wspLcdlGyqYwqaZnm4BStTRKIMLhy3t0BqidF5ZDH7BwxxrZTwZyiGpd4XCkHwD7cQiz9VdmwEvJk2aMH4-0x_maIXotk3fhetPzNJtfTlloj_ygNV8wQ8mw5A9hMHGRXKF7mo49JNhXBBessMrMO2190FpaUYAtaSucs6_fMccgtn27gMcet9l-nUwiHCMP-J8aS43VmFOMfmtVmcg4xlsvWs


Ensuite j'ai continué en suivant la doc : https://henixdevelopment.gitlab.io/squa ... stall.html qui dit :


En considérant qu'un Squash Orchestrator est lancé sur orchestrator.example.com, avec un jeton stocké dans la variable d'environnement TOKEN, la commande suivante enregistre l'environnement d'exécution Windows et recevra les commandes ciblant windows et/ou robotframework :


chcp 65001
opentf-agent --tags windows,robotframework --host http://orchestrator.example.com/ --token %TOKEN%
L'agent contactera l'orchestrateur toutes les 5 secondes, et exécutera les commandes receptionnées.
La commande chcp configure la console en Unicode. Il s'agit d'une spécificité Windows. Cette configuration peut être nécessaire suivant le framework de test disponible sur l'environnement d'exécution.


donc j'ai d'abord lancé la commande docker ps pour savoir ce qui était disponible :

Code : Tout sélectionner

C:\Users\IssamMERIKHI>docker ps
CONTAINER ID   IMAGE                                   COMMAND                  CREATED          STATUS          PORTS                                                                                                             NAMES
5a5b9afb09cf   squashtest/squash-orchestrator:latest   "python /app/tm-conn…"   19 minutes ago   Up 19 minutes   7796/tcp, 9464/tcp, 12312/tcp, 24368/tcp, 0.0.0.0:7774-7776->7774-7776/tcp, 0.0.0.0:38368->38368/tcp, 34537/tcp   orchestrator
et puis comme je ne sais pas trop j'ai essayé différent URL pour l'orchestrator :

C:\Users\IssamMERIKHI>opentf-agent --tags windows,robotframework --host http://127.0.0.1:7774/ --token %TOKEN%
INFO:root:OpenTestFactory Agent version 1.7.0.
WARNING:root:No encoding specified but console encoding is not 65001 (utf-8).
INFO:root:Registering agent on http://127.0.0.1:7774:24368/agents.
INFO:root:Could not reach http://127.0.0.1:7774:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:7774:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:7774:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:7774:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:7774:24368/agents, retrying.
ERROR:root:Failed to register to server: Failed to parse: http://127.0.0.1:7774:24368/agents.

puis j'ai testé ça :

C:\Users\IssamMERIKHI>opentf-agent --tags windows,robotframework --host http://127.0.0.1/ --token %TOKEN%
INFO:root:OpenTestFactory Agent version 1.7.0.
WARNING:root:No encoding specified but console encoding is not 65001 (utf-8).
INFO:root:Registering agent on http://127.0.0.1:24368/agents.
INFO:root:Could not reach http://127.0.0.1:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368/agents, retrying.
ERROR:root:Could not reach the orchestrator (HTTPConnectionPool(host='127.0.0.1', port=24368): Max retries exceeded with url: /agents (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000022186846E70>: Failed to establish a new connection: [WinError 10061] Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée'))). Is the orchestrator running?
ERROR:root:(Attempting to reach http://127.0.0.1:24368/agents)

et enfin j'ai essayé de mettre ça :

C:\Users\IssamMERIKHI>opentf-agent --tags windows,robotframework --host http://127.0.0.1:24368 --token %TOKEN%
INFO:root:OpenTestFactory Agent version 1.7.0.
WARNING:root:No encoding specified but console encoding is not 65001 (utf-8).
INFO:root:Registering agent on http://127.0.0.1:24368:24368/agents.
INFO:root:Could not reach http://127.0.0.1:24368:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368:24368/agents, retrying.
INFO:root:Could not reach http://127.0.0.1:24368:24368/agents, retrying.
ERROR:root:Failed to register to server: Failed to parse: http://127.0.0.1:24368:24368/agents.

J'ai l'impression de mettre des coups d'épée dans l'eau... une âme charitable pour me débloquer ?

Bonne journée à tous et bon week end :)
GambettaLimonade
Messages : 9
Inscription : mer. avr. 16, 2025 12:11 am

Re: Config automatisation Squash Orchestrator

Message par GambettaLimonade »

Ce qui est bizarre c'est qu'au moment ou je rentre le jeton côté Servers, les logs docker me disent :

[2025-04-18 13:16:13,443] WARNING in receptionist: Not a known format, expecting JSON or YAML.
[2025-04-18 13:16:13,464] WARNING in killswitch: Not a valid UUID.

Et en dessous dans la partie Environnements j'ai ça

1 the_environment_ip_or_hostname linux, robotframework, ssh UNREACHABLE

J'ai l'impression qu'il accepte mon token mais qu'il ne le "valide" pas si je peux me permettre un abus de langage...
Pourtant je pense suivre la doc officielle...
kung
Messages : 10
Inscription : mer. juil. 05, 2023 12:11 pm

Re: Config automatisation Squash Orchestrator

Message par kung »

Bonjour,

La documentation que vous avez utilisé est obsolète et date d'un petit moment (2021).

Voici un lien vers une documentation un peu plus récente, à noter que la documentation à utiliser va dépendre de la version de Squash TM : https://tm-fr.doc.squashtest.com/v9/ins ... stall.html

Dans votre cas, le port du service agentchannel permettant aux agents de s'enregistrer n'est pas ouvert, ce qui explique pourquoi vos commandes partent en erreur. Par défaut le port est le 24368, si vous utilisez la commande d'une documentation plus récente le port devrait être exposé (l'ouverture se fait dans la commande de lancement du container, avec l'option -p).

Une fois le port ouvert, juste relancer l'agent avec cette commande devrait suffire (le port est géré par l'option --port et est par défaut défini sur 24368) :

Code : Tout sélectionner

opentf-agent --tags windows,robotframework --host http://127.0.0.1 --token %TOKEN%
Les variables d'environnement SSH_CHANNEL_* définies au démarrage du container permettent d'indiquer un environnement d'exécution SSH. Elles ne sont pas obligatoires et ne doivent être définies que si vous souhaitez déclarer un environnement SSH. Il faut également que les informations renseignées soient correctes (et donc cibler un environnement joignable).

Concernant les différents WARNING, vous pouvez les ignorer si vous avez bien la liste des environnements affichés dans Squash TM. Selon la version de TM des requêtes incorrectes sont envoyées juste pour vérifier que les différents services de l'orchestrateur soient bien joignables.

Cordialement
Répondre

Revenir à « Intégration à la CI/CD »