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

[Ingest Management] Add Agent Flyout Does Not Always Display the Right Enrollment Token in Commands #72717

Closed
charlie-pichette opened this issue Jul 21, 2020 · 1 comment · Fixed by #73062
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@charlie-pichette
Copy link
Contributor

charlie-pichette commented Jul 21, 2020

Kibana version:
7.9.0 3e10432f5f8b (BC2) GCP Cloud Deploy

Elasticsearch version:
7.9.0 3e10432f5f8b (BC2

Browser version:
Chrome Version 84.0.4147.89 (Official Build) (64-bit)

Browser OS version:
MacOS 10.15.6 (19G73)

Original install method (e.g. download page, yum, from source, etc.):
Cloud Deploy

Describe the bug:
When there are multiple Agent configurations the Add Agent flyout does not always display the correct token in the commands listed.

Steps to reproduce:

  1. Navigate to Ingest and enable Fleet.
  2. Create a new configuration, name it Endpoint Prevent.
  3. Add the elastic endpoint integration to it.
  4. Create a new configuration, name it Endpoint Detect.
  5. Add the elastic endpoint integration to it.
  6. Click on the Add Agent button.
  7. Note the enrollment token in the commands listed at the bottom of the flyout.
  8. Select the second agent configuration. Note the enrollment token does not change in the commands.
  9. Select the third agent configuration. Note the enrollment token changes but it is not correct for the configuration selected.

Expected behavior:
The commands should always display the correct enrollment token.

Screenshots (if relevant):
The enrollment tokens:
Screen Shot 2020-07-21 at 1 02 45 PM

Then enrollment token for the second configuration:
Screen Shot 2020-07-21 at 1 16 11 PM

Screen capture of changing to different agent configs:

add_agent

Endpoint Detect uses YWtON2... (which is correct)
Endpoint Prevent uses YWtON2... (which is wrong, it belongs to Endpoint Detect)
Default uses dEVONG... (which is wrong, it belongs to Endpoint Prevent)
Endpoint Detect uses YjBONG... (which is wrong, it belongs to Default)
Endpoint Prevent uses YWtON2... (which is wrong, it belongs to Endpoint Detect)
Endpoint Detect uses dEVONG... (which is wrong, it belongs to Endpoint Prevent)

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:
Seems like it is only correct on the first entry to the flyout.

@charlie-pichette charlie-pichette added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team Ingest Management:beta1 labels Jul 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants