-
Notifications
You must be signed in to change notification settings - Fork 197
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
Console error when I have an agent selected and environment change #5745
Labels
Comments
10 tasks
This is a known issue, present in older versions of Wazuh. The use case for this feature needs to be reworked. This should not be a stopper for 4.5.0. |
10 tasks
10 tasks
10 tasks
10 tasks
This was referenced Sep 21, 2023
This was referenced Sep 27, 2023
2 tasks
This was referenced Oct 3, 2023
2 tasks
We will investigate the optimal solution for this in a future release. |
2 tasks
6 tasks
6 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
This fix will be fixed in this issue, that refactors the pinned agent management.
|
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
The goal of this test is to move between the environments without getting errors.
It is detected that when we have more agents in an environment and then we move them to another that has less, it generates an error.
This happens because if we select the agent with ID 002 in Env-1, and then move to Env-2, what it does is change the environments and keep agent ID 002 that there is inside Env-2.
Now, as in this case, Env-1 has 4 agents, and Env-2 only 2 agents. When I select the agent with ID 004 that exists in Env-1, and then I move to Env-2 as that ID does not exist, it generates the error.
I propose two solutions:
Note: Found on Demo environment 4.5.0 in testing E2E.
Preconditions
env-1
thanenv-2
Steps to reproduce
env-1
is selected.env-2
.env-1
toenv-2
.Expected Result
Actual Result
Screenshots
Details of Error: No agent information was returned (1701) - Agent does not exist
Details of Scenario with a video
The text was updated successfully, but these errors were encountered: