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 flow is not available on fresh kibana setup while adding first integration. #181800

Closed
amolnater-qasource opened this issue Apr 26, 2024 · 4 comments · Fixed by #182214
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high 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

Comments

@amolnater-qasource
Copy link

Kibana Build details:

VERSION: 8.14.0 BC2
BUILD: 73626
COMMIT: bcf6960778ae270d0894a8aab07f10197ee9b97f

Preconditions:

  1. 8.14.0-BC2 Kibana cloud environment should be available.

Steps to reproduce:

  1. Navigate to Integrations>Nginx.
  2. Add Nginx and observe new Add integration flow is not available.

Expected Result:
New Add integration flow should be available on fresh kibana setup while adding first integration.
image

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-04-26.12-14-21.mp4
@amolnater-qasource amolnater-qasource added bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Apr 26, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@manishgupta-qasource Please review.

@manishgupta-qasource
Copy link

Secondary review for this ticket is Done

@jen-huang jen-huang self-assigned this May 1, 2024
jen-huang added a commit that referenced this issue May 1, 2024
## Summary

Resolves #181800. Fixes the
logic for detecting first time Elastic Agent users on Cloud so that the
multi-page layout for adding an integration kicks in.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue May 1, 2024
…ic#182214)

## Summary

Resolves elastic#181800. Fixes the
logic for detecting first time Elastic Agent users on Cloud so that the
multi-page layout for adding an integration kicks in.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 63bc11a)
kibanamachine added a commit that referenced this issue May 1, 2024
…#182214) (#182281)

# Backport

This will backport the following commits from `main` to `8.14`:
- [[Fleet] Fix logic for detecting first time Elastic Agent users
(#182214)](#182214)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jen
Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2024-05-01T17:47:53Z","message":"[Fleet]
Fix logic for detecting first time Elastic Agent users (#182214)\n\n##
Summary\r\n\r\nResolves #181800.
Fixes the\r\nlogic for detecting first time Elastic Agent users on Cloud
so that the\r\nmulti-page layout for adding an integration kicks
in.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63bc11a02b0e25713a494bce8fdf225b64d94975","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v8.14.0","v8.15.0"],"title":"[Fleet]
Fix logic for detecting first time Elastic Agent
users","number":182214,"url":"https://github.com/elastic/kibana/pull/182214","mergeCommit":{"message":"[Fleet]
Fix logic for detecting first time Elastic Agent users (#182214)\n\n##
Summary\r\n\r\nResolves #181800.
Fixes the\r\nlogic for detecting first time Elastic Agent users on Cloud
so that the\r\nmulti-page layout for adding an integration kicks
in.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63bc11a02b0e25713a494bce8fdf225b64d94975"}},"sourceBranch":"main","suggestedTargetBranches":["8.14"],"targetPullRequestStates":[{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/182214","number":182214,"mergeCommit":{"message":"[Fleet]
Fix logic for detecting first time Elastic Agent users (#182214)\n\n##
Summary\r\n\r\nResolves #181800.
Fixes the\r\nlogic for detecting first time Elastic Agent users on Cloud
so that the\r\nmulti-page layout for adding an integration kicks
in.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63bc11a02b0e25713a494bce8fdf225b64d94975"}}]}]
BACKPORT-->

Co-authored-by: Jen Huang <its.jenetic@gmail.com>
@amolnater-qasource amolnater-qasource added the QA:Ready for Testing Code is merged and ready for QA to validate label May 2, 2024
@amolnater-qasource
Copy link
Author

Hi Team,

We have revalidated this issue on latest 8.14.0 BC4 kibana cloud environment and found it fixed now:

Observations:

  • New Add integration flow is available on fresh kibana setup while adding first integration.

Screen Recording:

Browse.integrations.-.Integrations.-.Elastic.-.Google.Chrome.2024-05-13.15-03-43.mp4

Build details:
VERSION: 8.14.0 BC4
BUILD: 73836
COMMIT: 23ed120

Hence we are marking this issue as QA:Validated.

Thanks!

@amolnater-qasource amolnater-qasource added QA:Validated Issue has been validated by QA and removed QA:Ready for Testing Code is merged and ready for QA to validate labels May 13, 2024
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:high Addressing this issue will have a high 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants