pro-akim
commented
5 months ago Update
Working first on https://github.com/wazuh/wazuh-qa/issues/5125
Closed rauldpm closed 3 months ago
pro-akim
commented
5 months ago Working first on https://github.com/wazuh/wazuh-qa/issues/5125
pro-akim
commented
5 months ago Allocation + All the agent tests (install,registration,restart,stop,uninstall) (no clean-up)
VAGRANT (1 Manager + 12 agents)
| CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|
| Test agent into all supported OS with one manager (RedHat 7) | 16min | 0 | 17min | 33min |
| Test agent into all supported OS with one manager (RedHat 8) | 13min | 0 | 19min | 32min |
| Test agent into all supported OS with one manager (RedHat 9) | 16min | 0 | 10min | 26min |
| Test agent into all supported OS with one manager (Centos 7) | 20min | 0 | 18min | 38min |
| Test agent into all supported OS with one manager (Centos 8) | 14min | 0 | 18min | 32min |
| Test agent into all supported OS with one manager (Debian 11) | 13min | 0 | 18min | 31min |
| Test agent into all supported OS with one manager (Debian 12) | 13min | 0 | 18min | 31min |
| Test agent into all supported OS with one manager (Ubuntu 20.04) | 18min | 0 | 18min | 36min |
| Test agent into all supported OS with one manager (Ubuntu 22.04) | 13min | 0 | 19min | 32min |
| Test agent into all supported OS with one manager (Oracle 9) | 13min | 0 | 20min | 23min |
| Test agent into all supported OS with one manager (Amazon Linux 2) | 13min | 0 | 20min | 33min |
| AWS (1 Manager + 13 agents) | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| Test agent into all supported OS with one manager (RedHat 7) | 5min | 0 | 41min | 46min | |
| Test agent into all supported OS with one manager (RedHat 8) | 5min | 0 | 46min | 51min | |
| Test agent into all supported OS with one manager (RedHat 9) | 8min | 0 | 44min | 56min | |
| Test agent into all supported OS with one manager (Centos 7) | 5min | 0 | 43min | 48min | |
| Test agent into all supported OS with one manager (Centos 8) | 5min | 0 | 45min | 50min | |
| Test agent into all supported OS with one manager (Debian 10) | 5min | 0 | 41min | 46min | |
| Test agent into all supported OS with one manager (Debian 11) | 6min | 0 | 36min | 42min | |
| Test agent into all supported OS with one manager (Debian 12) | 5min | 0 | 48min | 53min | |
| Test agent into all supported OS with one manager (Ubuntu 20.04) | None | 0 | 44min | None | |
| Test agent into all supported OS with one manager (Ubuntu 22.04) | 5min | 0 | 44min | 49min | |
| Test agent into all supported OS with one manager (Oracle 9) | 6min | 0 | 41min | 47min |
VAGRANT
| (Antonio localhost) | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| Part 1: install,register,restart,stop,uninstall on all agents with clean up (1 manager + 7 agents) | 10min | 7min | 17min | 34min | |
| Part 2: install,register,restart,stop,uninstall on all agents with clean up (1 manager + 6 agents) | 7min | 6min | 17min | 30min |
| (Federico localhost) | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| Part 1: install with provision and stop on all agents with clean up (1 manager + 7 agents) | 12min | 12min | 13min | 37min | |
| Part 2: install with provision and stop on all agents with clean up (1 manager + 6 agents) | 7min | 15min | 3min | 25min |
| (Antonio localhost) | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| Part 1: install with provision and restart on all agents with clean up (1 manager + 7 agents) | 7min | 22min | 4min | 33min | |
| Part 2: install with provision and restart on all agents with clean up (1 manager + 6 agents) | 7min | 12min | 4min | 23min | |
| Part 1: install with provision and uninstall on all agents with clean up (1 manager + 7 agents) | 7min | 11min | 14min | 32min | |
| Part 2: install with provision and uninstall on all agents with clean up (1 manager + 6 agents) | 7min | 13min | 5min | 25min |
| AWS | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| Part 1: install, register, restart,stop,uninstall on all agents with clean up (1 manager + 6 agents) | 1min?? 1 ec2 only | 2min | 27min | 30min | |
| Part 2: install, register, restart,stop,uninstall on all agents with clean up (1 manager + 7 agents) | 25seg ?? 1 ec2 only | 2min | 38min | 40min 25seg | |
| All: install with provision and stop on all agents with clean up (1 manager + 13 agents) | 6min | 27min | 14min | 47min | |
| All: install with provision and restart on all agents with clean up (1 manager + 13 agents) | 5min | 27min | 15min | 47min | |
| All: install with provision and uninstall on all agents with clean up (1 manager + 13 agents) | 6min | 27min | 23min | 56min |
VAGRANT
| (Antonio localhost) | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| 12 managers (install,stop,restart,uninstall) | 12min | 0 | 56min | 1h 8min |
| AWS | CASE | Allocation | Provision | Testing | Total |
|---|---|---|---|---|---|
| 11 managers (install,stop,restart,uninstall) | 3min | 0 | 58min | 1h 2min |
Lenovo ThinkPad T14 Gen 1 48Gib Memory Intel® Core™ i5-10310U CPU @ 1.70GHz × 8 Ubuntu 22.04.3 LTS 64bit
Lenovo ThinkPad L15 Gen 1 32Gib Memory Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz 20.04.1-Ubuntu LTS 64bit
pro-akim
commented
5 months ago Waiting for some definitions to move to the next analysis.
pro-akim
commented
5 months ago | 1 Manager | N Agent | Allocation (Time) | Provision (Time) | Testing (Time) | Clean-up (Time) | Total (Time) |
|---|---|---|---|---|---|---|
| 1 | 1 | 1m | 5m | 6m | 3m | 17m |
| 1 | 6 | 3m | 16m | 18m | 7m | 44m |
| 1 | 10 | 5m | 22m | 35m | 12m | 1h14m |
| 1 | 13 | 5m | 30m | 41m | 13m | 1h29m |
pro-akim
commented
5 months ago | N Manager | 0 Agent | Allocation (Time) | Provision (Time) | Testing (Time) | Clean-up (Time) | Total (Time) |
|---|---|---|---|---|---|---|
| 1 | 0 | -- | -- | -- | -- | -- |
| 6 | 0 | -- | -- | -- | -- | -- |
| 10 | 0 | -- | -- | -- | -- | -- |
| 13 | 0 | -- | -- | -- | -- | -- |
@pro-akim I modified the YAML input to fix some errors, I updated it, and here are the results:
pro-akim
commented
5 months ago Some error found in the provision:
[2024-04-11 17:44:00] [DEBUG] [585081] [ThreadPoolExecutor-0_0] [workflow_engine]: Running task "provision-manager-linux-oracle-9-amd64" with arguments: ['modules/provision/main.py', '--inventory=/tmp/dtt1-poc/manager-linux-oracle-9-amd64/inventory.yaml', "--install={'component': 'tar'}"]
[2024-04-11 17:44:03] [DEBUG] [585081] [ThreadPoolExecutor-0_0] [workflow_engine]: Finished task "provision-manager-linux-oracle-9-amd64" execution with result:
[2024-04-11 17:44:00] [DEBUG] ANSIBLE: Using inventory: {'all': {'hosts': {'ec2-52-23-206-224.compute-1.amazonaws.com': {'ansible_port': 2200, 'ansible_user': 'ec2-user', 'ansible_ssh_private_key_file': '/home/akim/Desktop/personal/Ephemeral'}}}}
[2024-04-11 17:44:00] [DEBUG] ANSIBLE: Running playbook: {'hosts': 'ec2-52-23-206-224.compute-1.amazonaws.com', 'become': True, 'gather_facts': True, 'tasks': [{'name': 'Capture ansible_os_family', 'set_fact': {'ansible_os_family': "{{ ansible_facts['distribution_file_variety'] }}", 'cacheable': 'yes'}}]}
No config file found; using defaults
PLAY [ec2-52-23-206-224.compute-1.amazonaws.com] *******************************
TASK [Gathering Facts] *********************************************************
fatal: [ec2-52-23-206-224.compute-1.amazonaws.com]: UNREACHABLE! => changed=false
msg: 'Failed to connect to the host via ssh: ssh: connect to host ec2-52-23-206-224.compute-1.amazonaws.com port 2200: No route to host'
unreachable: true
PLAY RECAP *********************************************************************
ec2-52-23-206-224.compute-1.amazonaws.com : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: Playbook {'hosts': 'ec2-52-23-206-224.compute-1.amazonaws.com', 'become': True, 'gather_facts': True, 'tasks': [{'name': 'Capture ansible_os_family', 'set_fact': {'ansible_os_family': "{{ ansible_facts['distribution_file_variety'] }}", 'cacheable': 'yes'}}]} finished with status {'skipped': {}, 'ok': {}, 'dark': {'ec2-52-23-206-224.compute-1.amazonaws.com': 1}, 'failures': {}, 'ignored': {}, 'rescued': {}, 'processed': {'ec2-52-23-206-224.compute-1.amazonaws.com': 1}, 'changed': {}}
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: Templates found: ['install.j2']
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: Rendering template install.j2
[2024-04-11 17:44:02] [WARNING] ANSIBLE: Template install.j2 not rendered
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: []
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: Using inventory: {'all': {'hosts': {'ec2-52-23-206-224.compute-1.amazonaws.com': {'ansible_port': 2200, 'ansible_user': 'ec2-user', 'ansible_ssh_private_key_file': '/home/akim/Desktop/personal/Ephemeral'}}}}
[2024-04-11 17:44:02] [DEBUG] ANSIBLE: Running playbook: {'hosts': 'ec2-52-23-206-224.compute-1.amazonaws.com', 'become': True, 'gather_facts': True, 'tasks': []}
No config file found; using defaults
PLAY [ec2-52-23-206-224.compute-1.amazonaws.com] *******************************
TASK [Gathering Facts] *********************************************************
fatal: [ec2-52-23-206-224.compute-1.amazonaws.com]: UNREACHABLE! => changed=false
msg: 'Failed to connect to the host via ssh: ssh: connect to host ec2-52-23-206-224.compute-1.amazonaws.com port 2200: No route to host'
unreachable: true
PLAY RECAP *********************************************************************
ec2-52-23-206-224.compute-1.amazonaws.com : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
[2024-04-11 17:44:03] [DEBUG] ANSIBLE: Playbook {'hosts': 'ec2-52-23-206-224.compute-1.amazonaws.com', 'become': True, 'gather_facts': True, 'tasks': []} finished with status {'skipped': {}, 'ok': {}, 'dark': {'ec2-52-23-206-224.compute-1.amazonaws.com': 1}, 'failures': {}, 'ignored': {}, 'rescued': {}, 'processed': {'ec2-52-23-206-224.compute-1.amazonaws.com': 1}, 'changed': {}}
[2024-04-11 17:44:03] [INFO] [585081] [ThreadPoolExecutor-0_0] [workflow_engine]: [provision-manager-linux-oracle-9-amd64] Finished task in 2.86 seconds.[root@ip-172-31-90-222 ec2-user]# uname -a
Linux ip-172-31-90-222.ec2.internal 5.15.0-101.103.2.1.el9uek.x86_64 #2 SMP Tue May 2 01:10:45 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux
[root@ip-172-31-90-222 ec2-user]# tar --version
bash: tar: command not foundThe EC2 is being provisioned but it is still not approachable by the provision, this error is related to that unavailability.
The Allocation module will have to check the EC2 before moving to the next step, then this issue will be blocked until that update.
Related issue: https://github.com/wazuh/wazuh-qa/issues/5198
rauldpm
commented
5 months ago After the daily meeting today, it has been discussed the time results, these comment result times include the stack (Wazuh manager, Filebeat, Wazuh dashboard, and Wazuh indexer) but the Testing module is only testing the Wazuh manager
The original idea of this issue was to check the flow using the Wazuh manager and Wazuh agent, we need to review this behavior as the flow should allow provisioning of the stack components individually, for example:
Those cases should contemplate installing the Filebeat, Wazuh dashboard, and Wazuh indexer (single or cluster), so the provision should generate certificates and copy them between nodes, also, the AIO deployment should be considered
If any of those cases are not contemplated in the current development, we should create an issue and discuss if it should be added for DTT1 or DTT2
rauldpm
commented
5 months ago Moved this issue to DTT1 as we need to test the threading fix
rauldpm
commented
5 months ago Updated https://github.com/wazuh/wazuh-qa/issues/5191#issuecomment-2049440225 with AWS results
Due to the thread bug issue, this issue will be edited so it reports the following data:
The parallel tests will have to report the same test cases (1-N, M-1) but for multiple threads {2, 4, 6, 8, 10), with this data, we will be able to determine which AWS instance type we need for the Jenkins CI
Blocked as internal due to We need to finish all other issues to have stable data
rauldpm
commented
4 months ago Moved ETA to 30/04/2024 as we need all DTT1 changes to test it correctly (main ETA 29/04/2024)
rauldpm
commented
4 months ago Moved ETA to 02/05/2024 as we need time to test the main branch: https://github.com/wazuh/wazuh-qa/issues/4495#issuecomment-2077142275
mhamra
commented
4 months ago --thread parameter with values 2, 3, 4 (parallel threads)| Test | Threads | Allocation (Time) | Provision (Time) | Testing (Time) | Clean-up (Time) | Total (Time) |
|---|---|---|---|---|---|---|
| Agents | 2 | -- | -- | -- | -- | -- |
| 3 | -- | -- | -- | -- | -- | |
| 4 | -- | -- | -- | -- | -- | |
| Managers | 2 | -- | -- | -- | -- | |
| 3 | -- | -- | -- | -- | ||
| 4 | -- | -- | -- | -- | ||
| AIO | 2 | -- | -- | -- | -- | -- |
| 3 | -- | -- | -- | -- | -- | |
| 4 | -- | -- | -- | -- | -- |
PLATFORMS:
Agent platform not included in the tests
PLATFORMS: (TBD)
PLATFORMS: (TBD)
rauldpm
commented
3 months ago Issue unblocked, as the 17 June is a holiday in Argentina, the issue's ETA is moved to 18 June, we will do general testing (each test will launch all available systems), for each deployment type (Agents, clusters, etc)
@fcaffieri please provide a log file for each test and an execution duration time for each test
pro-akim
commented
3 months ago Agent tests AWS --threads=4 Agent 4.7.4 live = False
pro-akim
commented
3 months ago Managers tests AWS --threads=4 Manager 4.7.4 live = False
Managers tests AWS no --threads Manager 4.7.4 live = False
pro-akim
commented
3 months ago Central component tests AWS no --threads Manager 4.7.4 live = False
pro-akim
commented
3 months ago After considering some fixes in the yaml:
18/06/2024 15:32:36 INFO: --- Wazuh server --- 18/06/2024 15:32:36 INFO: Starting the Wazuh manager installation. 18/06/2024 15:33:20 INFO: Wazuh manager installation finished. 18/06/2024 15:33:20 INFO: Wazuh manager vulnerability detection configuration finished. 18/06/2024 15:33:20 INFO: Starting service wazuh-manager. 18/06/2024 15:33:32 INFO: wazuh-manager service started. 18/06/2024 15:33:32 INFO: Starting Filebeat installation. 18/06/2024 15:33:42 INFO: Filebeat installation finished. curl: (22) The requested URL returned error: 404 18/06/2024 15:33:42 ERROR: Error downloading wazuh-template.json file. 18/06/2024 15:33:42 INFO: --- Removing existing Wazuh installation --- 18/06/2024 15:33:42 INFO: Removing Wazuh manager.
- Error related to Wazuh installation assistant and repository used, expected
----
After changes :red_circle:
Wazuh Manager has been correctly installed
Windows EC2 have been allocated, however the instances have been deleted due to lack of connection
[Windows error.log](https://github.com/user-attachments/files/15898157/Windows.error.log)
----
Running test only with Windows EC2s and Ubuntu Server :red_circle:
[jobflow.log](https://github.com/user-attachments/files/15898783/jobflow.log)
fcaffieri
commented
3 months ago The reported errors are due to the following:
root@stack-ubuntu2204-2:/home/vagrant# curl -sO https://packages-dev.wazuh.com/4.8/wazuh-install.sh
root@stack-ubuntu2204-2:/home/vagrant# bash ./wazuh-install.sh -a -i -o
06/18/2024 20:25:07 INFO: Starting Wazuh installation assistant. Wazuh version: 4.8.0
06/18/2024 20:25:07 INFO: Verbose logging redirected to /var/log/wazuh-install.log
06/18/2024 20:25:09 INFO: --- Removing existing Wazuh installation ---
06/18/2024 20:25:09 INFO: Wazuh GPG key not found in the system
06/18/2024 20:25:09 INFO: Installation cleaned.
06/18/2024 20:25:09 WARNING: Hardware and system checks ignored.
06/18/2024 20:25:21 INFO: Wazuh web interface port will be 443.
06/18/2024 20:25:32 INFO: Wazuh development repository added.
06/18/2024 20:25:32 INFO: --- Configuration files ---
06/18/2024 20:25:32 INFO: Generating configuration files.
06/18/2024 20:25:32 INFO: Generating the root certificate.
06/18/2024 20:25:33 INFO: Generating Admin certificates.
06/18/2024 20:25:33 INFO: Generating Wazuh indexer certificates.
06/18/2024 20:25:33 INFO: Generating Filebeat certificates.
06/18/2024 20:25:34 INFO: Generating Wazuh dashboard certificates.
06/18/2024 20:25:35 INFO: Created wazuh-install-files.tar. It contains the Wazuh cluster key, certificates, and passwords necessary for installation.
06/18/2024 20:25:35 INFO: --- Wazuh indexer ---
06/18/2024 20:25:35 INFO: Starting Wazuh indexer installation.
06/18/2024 20:27:15 INFO: Wazuh indexer installation finished.
06/18/2024 20:27:15 INFO: Wazuh indexer post-install configuration finished.
06/18/2024 20:27:15 INFO: Starting service wazuh-indexer.
06/18/2024 20:27:41 INFO: wazuh-indexer service started.
06/18/2024 20:27:41 INFO: Initializing Wazuh indexer cluster security settings.
06/18/2024 20:28:05 INFO: Wazuh indexer cluster security configuration initialized.
06/18/2024 20:28:05 INFO: Wazuh indexer cluster initialized.
06/18/2024 20:28:05 INFO: --- Wazuh server ---
06/18/2024 20:28:05 INFO: Starting the Wazuh manager installation.
06/18/2024 20:29:15 INFO: Wazuh manager installation finished.
06/18/2024 20:29:16 INFO: Wazuh manager vulnerability detection configuration finished.
06/18/2024 20:29:16 INFO: Starting service wazuh-manager.
06/18/2024 20:29:36 INFO: wazuh-manager service started.
06/18/2024 20:29:36 INFO: Starting Filebeat installation.
06/18/2024 20:29:44 INFO: Filebeat installation finished.
curl: (22) The requested URL returned error: 404
06/18/2024 20:29:44 ERROR: Error downloading wazuh-template.json file.
06/18/2024 20:29:44 INFO: --- Removing existing Wazuh installation ---
06/18/2024 20:29:44 INFO: Removing Wazuh manager.
06/18/2024 20:29:55 INFO: Wazuh manager removed.
06/18/2024 20:29:55 INFO: Removing Wazuh indexer.
06/18/2024 20:29:58 INFO: Wazuh indexer removed.
06/18/2024 20:29:58 INFO: Removing Filebeat.
06/18/2024 20:29:59 INFO: Filebeat removed.
06/18/2024 20:30:00 INFO: Installation cleaned.
root@stack-ubuntu2204-2:/home/vagrant#
These were the errors reported, which are due to incorrect execution of the tests, since what is going to be tested with these tests are unreleased packages, in this case if the parameter live = False is used and for the released packages live = True and the latest released version must be used.
fcaffieri
commented
3 months ago Full Log:
Summary Result:
| Agent | Test result |
|---|---|
| linux-redhat-7-amd64 | :green_circle: |
| linux-redhat-7-arm64 | :green_circle: |
| linux-redhat-8-amd64 | :green_circle: |
| linux-redhat-8-arm64 | :green_circle: |
| linux-redhat-9-amd64 | :green_circle: |
| linux-redhat-9-arm64 | :green_circle: |
| linux-centos-7-amd64 | :green_circle: |
| linux-centos-7-arm64 | :green_circle: |
| linux-centos-8-amd64 | :green_circle: |
| linux-centos-8-arm64 | :green_circle: |
| linux-debian-10-amd64 | :green_circle: |
| linux-debian-10-arm64 | :green_circle: |
| linux-debian-11-amd64 | :green_circle: |
| linux-debian-11-arm64 | :green_circle: |
| linux-debian-12-amd64 | :green_circle: |
| linux-debian-12-arm64 | :green_circle: |
| linux-ubuntu-22.04-amd64 | :green_circle: |
| linux-ubuntu-22.04-arm64 | :green_circle: |
| linux-ubuntu-18.04-amd64 | :green_circle: |
| linux-ubuntu-18.04-arm64 | :green_circle: |
| linux-ubuntu-20.04-amd64 | :green_circle: |
| linux-ubuntu-20.04-arm64 | :green_circle: |
| linux-oracle-9-amd64 | :green_circle: |
| linux-amazon-2-amd64 | :green_circle: |
| linux-amazon-2-arm64 | :green_circle: |
| linux-amazon-2023-amd64 | :green_circle: |
| linux-amazon-2023-arm64 | :green_circle: |
| windows-server-2012r2-amd64 | :red_circle: |
| windows-server-2016-amd64 | :red_circle: |
| windows-server-2019-amd64 | :red_circle: |
| macos-ventura-13-amd64 | :red_circle: |
| macos-sonoma-14-amd64 | :red_circle: |
The Windows tests failed because the test module could not connect to the VMs and the allocator could not raise them correctly. The DevOps team was contacted to validate why it could not raise the VMS, but the tests worked right.
Full Log:
Summary Result:
| Agent | Test result |
|---|---|
| linux-ubuntu-20.04-amd6 | :green_circle: |
| linux-ubuntu-22.04-amd6 | :green_circle: |
| linux-redhat-7-amd64 | :green_circle: |
| linux-redhat-8-amd64 | :green_circle: |
| linux-redhat-9-amd64 | :green_circle: |
| linux-amazon-2-amd64 | :green_circle: |
| linux-centos-8-amd64 | :green_circle: |
| linux-centos-7-amd64 | :green_circle: |
| linux-debian-10-amd64 | :green_circle: |
| linux-debian-11-amd64 | :green_circle: |
| linux-debian-12-amd64 | :green_circle: |
| Agent | Test result |
|---|---|
| linux-ubuntu-20.04-amd64 | :green_circle: |
| linux-ubuntu-22.04-amd64 | :green_circle: |
| linux-amazon-2-amd64 | :green_circle: |
| linux-redhat-7-amd64 | :green_circle: |
| linux-redhat-8-amd64 | :green_circle: |
| linux-redhat-9-amd64 | :green_circle: |
| linux-centos-7-amd64 | :green_circle: |
| linux-centos-8-amd64 | :green_circle: |
| linux-debian-10-amd64 | :green_circle: |
| linux-debian-11-amd64 | :green_circle: |
| linux-debian-12-amd64 | :green_circle: |
Full Log:
pro-akim
commented
3 months ago After a brief conversation with David Correa, it was decided to open an issue for analysis
By changing pywinrm from 0.4.0 to 0.4.3 (LTS), it worked
pro-akim
commented
3 months ago Command:
python3 -m jobflow modules/jobflow/examples/agent/aws/test-agent-complete.yaml --threads=4Full Log:
Summary Result:
| Agent | Test result |
|---|---|
| linux-redhat-7-amd64 | :green_circle: |
| linux-redhat-7-arm64 | :green_circle: |
| linux-redhat-8-amd64 | :green_circle: |
| linux-redhat-8-arm64 | :green_circle: |
| linux-redhat-9-amd64 | :green_circle: |
| linux-redhat-9-arm64 | :green_circle: |
| linux-centos-7-amd64 | :green_circle: |
| linux-centos-7-arm64 | :green_circle: |
| linux-centos-8-amd64 | :green_circle: |
| linux-centos-8-arm64 | :green_circle: |
| linux-debian-10-amd64 | :green_circle: |
| linux-debian-10-arm64 | :green_circle: |
| linux-debian-11-amd64 | :green_circle: |
| linux-debian-11-arm64 | :green_circle: |
| linux-debian-12-amd64 | :green_circle: |
| linux-debian-12-arm64 | :green_circle: |
| linux-ubuntu-22.04-amd64 | :green_circle: |
| linux-ubuntu-22.04-arm64 | :green_circle: |
| linux-ubuntu-18.04-amd64 | :green_circle: |
| linux-ubuntu-18.04-arm64 | :green_circle: |
| linux-ubuntu-20.04-amd64 | :green_circle: |
| linux-ubuntu-20.04-arm64 | :green_circle: |
| linux-oracle-9-amd64 | :green_circle: |
| linux-opensuse-15-amd64 | :green_circle: |
| linux-amazon-2-amd64 | :green_circle: |
| linux-amazon-2-arm64 | :green_circle: |
| linux-amazon-2023-amd64 | :green_circle: |
| linux-amazon-2023-arm64 | :green_circle: |
| windows-desktop-10-amd64 | :green_circle: |
| windows-server-2012r2-amd64 | :green_circle: |
| windows-server-2016-amd64 | :green_circle: |
| windows-server-2019-amd64 | :green_circle: |
| windows-server-2022-amd64 | :green_circle: |
| macos-ventura-13-amd64 | :green_circle: |
| macos-sonoma-14-amd64 | :green_circle: |
fcaffieri
commented
3 months ago | Test | Allocation | Provision | Testing |
|---|---|---|---|
| Full agent test (35 agents) | 25 min | 7min | 52 min |
| Test | Allocation | Provision | Testing |
|---|---|---|---|
| Full agent test (35 agents) | 20 min | 8min | 23 min |
| Test | Allocation | Provision | Testing |
|---|---|---|---|
| Full Manager test (11 managers) | 4 min | - | 6 min |
| Test | Allocation | Provision | Testing |
|---|---|---|---|
| Full Central component test (11 systems with central components) | 5 min | - | 20 min |
fcaffieri
commented
3 months ago LGTM
rauldpm
commented
3 months ago LGTM
Description
We need to perform an analysis of DTT1 functionality and execution times so that we have reference times. The idea of this issue is to collect information about the branch's status.
Related:
Tasks