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

System Test - Wazuh DB (T0): Agent forced to change group #2512

Closed
Tracked by #2504
damarisg opened this issue Jan 31, 2022 · 2 comments · Fixed by #2668
Closed
Tracked by #2504

System Test - Wazuh DB (T0): Agent forced to change group #2512

damarisg opened this issue Jan 31, 2022 · 2 comments · Fixed by #2668

Comments

@damarisg
Copy link
Member

damarisg commented Jan 31, 2022

Description

The aimhere is to verify that in a synchronized environment with N agents belonging to different groups, we force the group change of an agent in a worker node (wdb).

Test Details

Case 1:

Given a configured master
And a worker1 worker configured
And a worker2 worker configured
And the agent AA registers with group A to the master node
And the agent AB registers with group B to the master node
And the agent AC registers with group C to the master node
And the cluster is synchronized
When the agent AA registered is force to change group B (force with wdb command)
Then the master has an AA agent with group B after X seconds
And the worker1 has an AA agent with group B after X seconds
And the worker2 has an AA agent with group B after X seconds

Case 2:

Given a configured master
And a worker1 worker configured
And a worker2 worker configured
And the agent AA registers with group A to the worker2 worker node
And the agent AB registers with group B to the worker1 worker node
And the agent AC registers with group C to the worker1 worker node
And the cluster is synchronized
When the agent AA registered is force to change group B (force with wdb command)
Then the master has an AA agent with group B after X seconds
And the worker1 has an AA agent with group B after X seconds
And the worker2 has an AA agent with group B after X seconds

Case 3:

Given a configured master
And a worker1 worker configured
And a worker2 worker configured
And the agent AA registers with group A to the worker2 worker node
And the agent AB registers with group B to the worker1 worker node
And the agent AC registers with group D to the worker1 worker node
And the cluster is synchronizing
When the agent AA registered is force to change group B (force with wdb command)
And the agent AA registered is force to change group C (force with wdb command)
And the cluster is synchronized after Z seconds
Then the worker1 has an AA agent with group C after X seconds
And the worker2 has an AA agent with group C after X seconds
And the master has an AA agent with group C after X seconds

Note:

  • X: Estimated time for complete information synchronization, minimum 2*Z --- worker1 -> master -> worker1/2
  • Z: Cluster synchronization period (default 10 seconds)
@Deblintrake09
Copy link
Contributor

Deblintrake09 commented Feb 11, 2022

Update 2022/02/14

  • Worked on branch tmp-2512-test-force-agent-group-change
  • Added set-agent-groups command
  • Move to blocked because of Wazuh/Wazuh #10771

Update 2022/02/11

  • Designed and blocked in the tests
  • On Hold waiting for command to use from Core Team

@damarisg
Copy link
Member Author

It was merged on qa-10771-agent-groups-files-to-wazuh-db branch and closed.

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.

3 participants