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

[Fleet]: New Add integration flyout gets stuck at confirm agent enrollment and fails to sync with installed Standalone agent. #134337

Closed
ghost opened this issue Jun 14, 2022 · 5 comments · Fixed by #134474
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team v8.3.0

Comments

@ghost
Copy link

ghost commented Jun 14, 2022

Kibana version: 8.3 Snapshot Kibana cloud environment

Host OS and Browser version: All, All

Build details:

VERSION: 8.3 Snapshot
BUILD: 53383
COMMIT: 492b369
Artifact Link: https://artifacts-api.elastic.co/v1/search/8.3-SNAPSHOT

Preconditions:

  • 8.3 Snapshot Kibana cloud environment should be available.
  • Fresh Kibana should be setup.
  • No agent should be installed.

Steps to reproduce:

  1. Login to Kibana environment.
  2. Navigate to Integrations tab and search Nginx integration.
  3. Click Add Nginx integration button
  4. Select Standalone mode and install a standalone agent with provided steps.
  5. Observe step 3 fails to sync with installed standalone agent.
  6. User gets stuck at this page.

What's working fine:
On navigating to Fleet>Data streams tab user is able to view data for standalone agent.

Expected Result:

  • New Add integration flyout should not get stuck at confirm agent enrollment and should be able to sync with installed standalone agent.

Screenshot:
1

2

@ghost ghost added bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Jun 14, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@ghost
Copy link
Author

ghost commented Jun 14, 2022

@manishgupta-qasource Please review

@manishgupta-qasource
Copy link

Secondary review for this ticket is Done

@jen-huang
Copy link
Contributor

@hop-dev I validated that we are showing the "confirm enrollment" step in the standalone instructions 🤔 Pretty sure we tested this previously though.. anyway, assigning to you to take a look:

image

@ghost
Copy link
Author

ghost commented Jun 22, 2022

Hi @hop-dev
We have validated this issue on 8.3 Snapshot and fount it fixed now.

  • Confirm incoming data step is removed for standalone first integration flow
  • User is able to complete first integration flow for standalone agent.

Build Details:
Version: 8.3 Snapshot
BUILD: 53487
COMMIT: b6dbc77
Artifact link: https://artifacts-api.elastic.co/v1/search/8.3-SNAPSHOT

Screen Recording:

Add.integration.-.Nginx.-.Integrations.-.Elastic.-.Google.Chrome.2022-06-22.12-56-41.mp4

Hence, marking this issue as QA:Validated

Thanks

@ghost ghost added the QA:Validated Issue has been validated by QA label Jun 22, 2022
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 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team v8.3.0
Projects
None yet
4 participants