You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are going to check that the integration tests of the 4.2 branch of wazuh-qa work correctly using the 4.2.2-rc1 version of wazuh.
The tests will be performed both in the local environment and in Jenkins using CentOS as the manager OS. As for the agents, Linux, Windows and macOS will be used as required.
Package info
Type
Format
Architecture
Versión
Revision
Tag
File name
Server
rpm
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh-manager-4.2.2-1.x86_64.rpm
Agent
rpm
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh-agent-4.2.2-1.x86_64.rpm
Agent
msi (Windows)
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh-agent-4.2.2-1.msi
Agent
wpk Windows
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh_agent_v4.2.2_windows.wpk
Agent
wpk Linux
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh_agent_v4.2.2_linux_x86_64.wpk
Agent
pkg (macOS)
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh-agent-4.2.2-1.pkg
Agent
p5p (Solaris 11)
x86_64
v4.2.2
40215
v4.2.2-rc1
wazuh-agent_v4.2.2-sol11-i386.p5p
Tests Integration - Status
References
Color
Status
🟢
All tests passed successfully
🟡
All tests passed but there are some warnings
🔴
Some tests have failures or errors
🔵
Test execution in progress
⚫
To Do
Test Integration - Results
Name
Local
OS
Linux
Windows
Solaris
macOS
Target
Manager
Agent
Agent
Agent
Agent
active_response
🟢
🟢
🟢
NA
NA
agentd
NA
🟢
🟢
NA
NA
analysisd
🟢
NA
NA
NA
NA
api
🟢
NA
NA
NA
NA
authd
🟢
NA
NA
NA
NA
FIM - BLOCKED
⚫
⚫
⚫
⚫
⚫
gcloud
🔴
NA
NA
NA
NA
logtest
🟢
NA
NA
NA
NA
remoted
🟢
NA
NA
NA
NA
rids
🟢
NA
NA
NA
NA
rootcheck
🟢
NA
NA
NA
NA
vulnerability_detector
🟢
NA
NA
NA
NA
wazuh_db
🟢
NA
NA
NA
NA
wpk
🔴
🟢
🟢
NA
NA
Details of Test Results Test Results - Active Response
ResultsAgentdWindows - In the first instance, It failed, but to verify that it was not working, it ran on Jenkins, where it worked successfully. So we estimate that the failure was in the local environment where it was ran. At this time, we are investigating what may have been the cause. For this reason, we change the status from Failure to Pass. We attach each detail of the executions in its section. We create a new issue to research it
ResultsGCloud - First, we thought that the problem was with our Repo, but after executed on 4.2.1 we saw that it works successfully. To check again, we ran the same test but on 4.2.2 on Jenkins, and it failed. We open a new issue to research what happens with this.
ResultsWPKManager - After a lot of changes applied on wazuh-qa some fixes couldn't apply and for that reason, these tests failed. We create a new issue to fix it. This failure isn't of 4.2.2 else our QA Repository.
Notes:
To have more details about 4.2.0-rc8 and 4.2.1-rc13, you could see on:
Description
We are going to check that the integration tests of the
4.2
branch ofwazuh-qa
work correctly using the4.2.2-rc1
version ofwazuh
.The tests will be performed both in the local environment and in Jenkins using
CentOS
as the manager OS. As for the agents,Linux
,Windows
andmacOS
will be used as required.Package info
Tests Integration - Status
References
Test Integration - Results
Details of Test Results
Test Results - Active Response
Test Results - Agentd
Test Results - Analysisd
Test Results - API
Test Results - Authd
Test Results - FIM
Test Results - Gcloud
Test Results - Logtest
Test Results - Remoted
Test Results - RIDS
Test Results - Rootcheck
Test Results - Vulnerability detector
Test Results - WazuhDB
Test Results - WPK
Versions Status
Note: Related to GCloud, the problems are with the credentials.
Failures Description
Notes:
To have more details about
4.2.0-rc8
and4.2.1-rc13
, you could see on:The text was updated successfully, but these errors were encountered: