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

Add coverage to group_sync_status updated correctly on each node #3953

Closed
QU3B1M opened this issue Feb 16, 2023 · 3 comments · Fixed by #4143
Closed

Add coverage to group_sync_status updated correctly on each node #3953

QU3B1M opened this issue Feb 16, 2023 · 3 comments · Fixed by #4143

Comments

@QU3B1M
Copy link
Member

QU3B1M commented Feb 16, 2023

Target version Related issue Related PR
4.4.0 #16190 #16202

Description

System tests should be developed to validate the group_sync_status is updated correctly on each cluster's node after a group where the agents are assigned is altered.

Proposed test cases

Group sync status - status updated correctly
Given a wazuh-cluster with 2 workers.
And 10k wazuh-agent connected to each node all assigned to the same 3 groups.
When a group folder is deleted in the "<node>".
Then immediately group_sync_status is in "<first_status>" on all agents.
And after the cluster is sync the group_sync_status is "<final_status>"

Examples:
  | node     | first_status | final_status  |
  |----------|--------------|---------------|
  | master   | synreq       | synced        |
  | worker-1 | synced       | synced        |
  | worker-2 | synced       | synced        |
@pro-akim pro-akim linked a pull request Apr 13, 2023 that will close this issue
@wazuhci wazuhci moved this to Backlog in Release 4.4.2 Apr 21, 2023
@wazuhci wazuhci moved this from Backlog to Pending final review in Release 4.4.2 Apr 24, 2023
pro-akim added a commit that referenced this issue Apr 27, 2023
pro-akim added a commit that referenced this issue May 2, 2023
@pro-akim pro-akim linked a pull request May 2, 2023 that will close this issue
pro-akim added a commit that referenced this issue May 2, 2023
pro-akim added a commit that referenced this issue May 2, 2023
@pro-akim pro-akim linked a pull request May 2, 2023 that will close this issue
pro-akim added a commit that referenced this issue May 4, 2023
pro-akim added a commit that referenced this issue May 4, 2023
pro-akim added a commit that referenced this issue May 4, 2023
pro-akim added a commit that referenced this issue May 5, 2023
pro-akim added a commit that referenced this issue May 5, 2023
pro-akim added a commit that referenced this issue May 5, 2023
pro-akim added a commit that referenced this issue May 10, 2023
pro-akim added a commit that referenced this issue Jul 3, 2023
pro-akim added a commit that referenced this issue Jul 3, 2023
pro-akim added a commit that referenced this issue Jul 3, 2023
pro-akim added a commit that referenced this issue Jul 3, 2023
@davidjiglesias
Copy link
Member

It has to be merged into 4.8.0, careful with changelog if applicable.

@wazuhci wazuhci moved this to On hold in Release 4.8.0 Sep 6, 2023
@wazuhci wazuhci moved this from On hold to In progress in Release 4.8.0 Sep 6, 2023
pro-akim added a commit that referenced this issue Sep 6, 2023
@pro-akim
Copy link
Member

pro-akim commented Sep 6, 2023

Update

Rebased to 4.8.0

@wazuhci wazuhci moved this from In progress to Pending final review in Release 4.8.0 Sep 6, 2023
@davidjiglesias
Copy link
Member

LGTM!

@wazuhci wazuhci moved this from Pending final review to Done in Release 4.8.0 Sep 8, 2023
@wazuhci wazuhci removed this from Release 4.8.0 Sep 13, 2023
@wazuhci wazuhci moved this to Done in Release 4.8.0 Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment