-
Notifications
You must be signed in to change notification settings - Fork 154
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
[Fleet]: User is able to add duplicate tags to Agents #858
Comments
Pinging @elastic/fleet (Team:Fleet) |
@manishgupta-qasource Please review |
Secondary review for this ticket is Done |
The enroll command is not maintained by kibana, redirecting this issue to elastic-agent project. |
Hi @jlind23, We have re-validated this issue on the latest 8.6.0 SNAPSHOT Kibana Staging environment and found that the issue is still reproducible. Below are the observations:
Screenshots: Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-12-28.13-50-35.mp4Build details:
Please let us know if anything else is required from our end. Thanks! |
Hi @cmacknz We have revalidated this issue on latest 8.10.0 SNAPSHOT kibana cloud environment and found it still reproducible. Observations:
Could you please confirm if there will be any update in the agent installation command? Build details: Please let us know if anything else is required from our end. cc: @jlind23 |
@amolnater-qasource I do think this is a "bug" but I don't see any urgency here so I will put that in our backlog. |
Hi Team, We have re-validated this issue on the latest 8.12.0 SNAPHOT Kibana cloud environment and found it fixed now. Observations:
Build details: Hence, we are marking this issue as QA:Validated. |
Kibana version: 8.4 Snapshot Kibana cloud environment
Host OS and Browser version: All, All
Build Details:
Preconditions:
Steps to reproduce:
.\elastic-agent.exe install --url=xxxxx:443 --enrollment-token=xxxxx --tag=win,win2,flag,class,happy,abc,XYZ,network,class
Expected Result:
Screenshots:
Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-08-04.13-22-24.mp4
The text was updated successfully, but these errors were encountered: