Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIM Windows Agent - Case: Check files are ignored in subdirectory according to configuration. #1889

Closed
4 tasks done
damarisg opened this issue Sep 13, 2021 · 2 comments · Fixed by #1929
Closed
4 tasks done
Assignees

Comments

@damarisg
Copy link
Member

damarisg commented Sep 13, 2021

Description

FIM tests has a lot of tests to fix because fails inconsistent times.

Related to
#1873

Pipeline parameters

Jenkins branch QA branch
v4.2.1-rc1 1873-4.2.1-fim-windows-agent

Packages details

Packages Info

Type Format Architecture Versión Revision Tag File name
Server rpm x86_64 v4.2.1 40214 v4.2.1 wazuh-manager-4.2.1-0.1873.x86_64.rpm
Agent rpm x86_64 v4.2.1 40214 v4.2.1 wazuh-agent-4.2.1-0.1873.x86_64.rpm
Agent msi (Windows) x86_64 v4.2.1 40214 v4.2.1 wazuh-agent-4.2.1-0.1873.msi
Agent pkg (macOS) x86_64 v4.2.1 40214 v4.2.1 wazuh-agent-4.2.1-0.1873.pkg
Agent p5p (Solaris 11) x86_64 v4.2.1 40214 v4.2.1 wazuh-agent_v4.2.1-0.1873-sol11-i386.p5p​
Agent p5p (Solaris 10) x86_64 v4.2.1 40214 v4.2.1 wazuh-agent_v4.2.1-0.1873-sol10-i386.pkg
Agent wpk (Linux) x86_64 v4.2.1 40214 v4.2.1 wazuh_agent_v4.2.1-0.1873_linux_x86_64.wpk
Agent wpk (Windows) x86_64 v4.2.1 40214 v4.2.1 wazuh_agent_v4.2.1-0.1873_windows.wpk

Note: The tag is v4.2.1 but for now, to create it on jenkins you need to use v4.2.1-rc1.

local_internal_options.conf

Manager

syscheck.debug=2
analysisd.debug=2
monitord.rotate_log=0

Agent

agent.debug=2
syscheck.debug=2
monitord.rotate_log=0

Environment

Provider Box OS CPU Memory
Vagrant "gusztavvargadr/windows-10" Windows 2 2048

pytest_args

-v --tier 0 --tier 1 --tier 2 --fim_mode="realtime" --fim_mode="whodata"

Development

Fix test_fim/test_files/test_ignore/test_ignore_valid.py to Windows.

If the test work successfully after 2 times, you should see if other member could be verify that it woks successfully.

Tasks

  • Research about the Test Case.
  • Fix the Test Case.
  • Verify that each execution works successfully. (Full Green - Attach evidence.)
  • Verify that cover scheduled, realtime, and whodata. Research if this case require all args, or only one.
@Deblintrake09
Copy link
Contributor

Deblintrake09 commented Sep 23, 2021

** Test Results **

Results Date By Status Notes
ResultsIgnoreValid.zip 2021/09/22 @Deblintrake09 🔴 2 Test runs in this file. Both red. 72 fails and 63 fails).

Research results

  • Started 2 test runs - both failed several tests (72 Fails, and 63 Fails).
  • Test execution is inconsistent between runs.
  • I suppose it's related to it all working through FileMonitor that and how many lines it reads before the timeout.
  • Will try increasing timeout delay to see if the logs are being written and not read (since logs are truncated and deleted after timeout it's impossible to know if it has appeared after the timeout.

** Test Results **

Results Date By Status Notes
ResultsIgnoreValid20Sec.zip 2021/09/23 @Deblintrake09 🟢 Timeout = 20 seconds
ResultsIgnoreValid20Sec2.zip 2021/09/23 @Deblintrake09 🟢 Timeout = 20 seconds
ResultsIgnoreValid20Sec3.zip 2021/09/23 @Deblintrake09 🟢 Timeout = 20 seconds

@damarisg
Copy link
Member Author

Closed by #1929

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants