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]: Policy is not selected under Add agent flyout when only one policy exists. #131121

Closed
amolnater-qasource opened this issue Apr 28, 2022 · 7 comments · Fixed by #133711
Closed
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

Comments

@amolnater-qasource
Copy link

Kibana version: 8.3 Snapshot Kibana cloud environment

Host OS and Browser version: Windows, All

Build details:

VERSION: 8.3.0
BUILD: 52349
COMMIT: eaf47aeb1af9b935685fe12f5591be498999a9ab

Preconditions:

  1. 8.2 Snapshot Kibana cloud environment should be available.
  2. Agent policy 1 should already be created.

Steps to reproduce:

  1. Login to Kibana environment.
  2. Navigate to Fleet>Agents tab.
  3. Click Add agent button and observe no policy is selected.

Expected Result:
As per feature #108456 when only one policy exists it should be selected itself under Add agent flyout.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-04-28.13-28-08.mp4

(Policy is visible in Add agent flyout dropdown but not visible in screen recording)
Working fine on 8.2:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-04-28.13-21-24.mp4
@amolnater-qasource amolnater-qasource 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 Apr 28, 2022
@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

@juliaElastic juliaElastic self-assigned this May 25, 2022
@juliaElastic
Copy link
Contributor

@amolnater-qasource @jen-huang I'm not sure it is a good idea to fix this right now, because if there is only one policy with fleet server integration, that would be auto selected, and the user will be stuck and can't go back to selecting a non-fleet server policy due to this issue

@jen-huang
Copy link
Contributor

@juliaElastic Could we auto-select the first non-Fleet Server policy if it exists?

@juliaElastic
Copy link
Contributor

juliaElastic commented Jun 7, 2022

@jen-huang Yes, we can partially solve the issue by auto-selecting only if the policy does not have Fleet Server integration.

@amolnater-qasource
Copy link
Author

Hi @hop-dev @jen-huang
We have revalidated this issue on latest 8.3 BC5 Kibana cloud environment and found it fixed now.

  • Policy is selected itself under Add agent flyout when only one policy exists.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-06-21.13-51-49.mp4

Build details:
BUILD: 53457
COMMIT: ba70bdf

Hence marking this 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 Jun 21, 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants