wazuh-qa icon indicating copy to clipboard operation
wazuh-qa copied to clipboard

Published 20 hours ago • verified publisher icon wazuh

Change manager Vulnerability Detector E2E test case logs are truncated

Open Rebits opened this issue 1 year ago • 5 comments

Description

It has been detected in Release 4.8.0 - RC 1 - Vulnerability Detection E2E tests, that the test case test_change_agent_manager is truncating the agent/manager logs, making difficult to get any information of the environment in case of failure.

Rebits avatar May 07 '24 13:05 Rebits

Investigating the truncation process, we can see that:

  1. In conftest.py file, clean_environment_logs and clean_environment_logs_function: both functions perform similar actions but have a different scope. They manage logs by deleting them at the end of their scope using truncate_remote_host_group_files.

  2. In logs.py file, truncate_remote_host_group_files: this function directly handles log deletion. It takes parameters to decide which host group and file types should be truncated.

  3. In file.py file, truncate_file: this function performs the action of opening the specified file in write mode, which automatically truncates the file.

To carry out this issue a conditional will be added to the clean_environment_logs function so that when the test_change_agent_manager case is performed it avoids truncation.

santipadilla avatar May 08 '24 16:05 santipadilla

Test before changes

  • Truncating logs for the test_change_agent_manager case

report.zip

Test after changes

  • Without truncating logs for the test_change_agent_manager case

report.zip

  • Known test failures: https://github.com/wazuh/wazuh-qa/issues/5319

santipadilla avatar May 09 '24 09:05 santipadilla

Changes made in this branch: fix/5345-skip-truncate-test-change-agent-manager In this PR: https://github.com/wazuh/wazuh-qa/pull/5355

santipadilla avatar May 09 '24 12:05 santipadilla

LGTM

rafabailon avatar May 09 '24 14:05 rafabailon

Moved ETA due to final review

santipadilla avatar May 10 '24 06:05 santipadilla

During a meeting with @santipadilla, we identified that the new agent configuration isn't properly applied after the configured agent is permuted because the agent isn't restarted following the change. It's likely that the restart agent call was inadvertently omitted during a merge or PR review.

The solution appears straightforward: ensure that agents are restarted after the permutate_manager fixture is applied.

Updated the issue title accordingly

[!WARNING] It's imperative to rerun this test in the E2E environment. Unfortunately, a current bug in RC1 (https://github.com/wazuh/wazuh/issues/23301) is hindering the appearance of some vulnerabilities. Therefore, we'll need to wait until this issue is resolved before verifying if there are any product-related issues concerning the manager change.

Rebits avatar May 13 '24 09:05 Rebits

Update

Test before modifying permutate_agents_managers fixture

report.zip

Test after modifying permutate_agents_managers fixture

report.zip

Test with only test_change_agent_manager case

report.zip

santipadilla avatar May 13 '24 10:05 santipadilla

New changes made in this branch: fix/5345-skip-truncate-test-change-agent-manager In this PR: https://github.com/wazuh/wazuh-qa/pull/5355

santipadilla avatar May 13 '24 13:05 santipadilla