elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.73k stars 8.14k forks source link

[Fleet]: Fleet Server policy is not visible under Agents tab without refreshing when the fleet server is installed with a policy created from Add Fleet Server flyout. #137932

Open amolnater-qasource opened 2 years ago

amolnater-qasource commented 2 years ago

Kibana version: 8.4 BC-1 Kibana cloud environment

Host OS and Browser version: All, All

Build details:

VERSION: 8.4.0
BUILD: 54999
COMMIT: 58f7eaf0f8dc3c43cbfcd393e587f155e97b3d0d
Artifact Link: https://staging.elastic.co/8.4.0-91109cf0/summary-8.4.0.html

Preconditions:

  1. 8.4 BC1 Kibana cloud environment should be available.

Steps to reproduce:

  1. Login to Kibana environment.
  2. Navigate to Agents tab>Add Fleet Server flyout.
  3. Add host and create a new Policy from here.
  4. Scroll down and install fleet server with the command available.
  5. Observe fleet server is installed however the policy name is not visible.
  6. Navigate to some other tab and navigate back to Agents tab(or simply hard refresh).
  7. Observe now Agent policy name is visible.

Expected Result: Fleet Server policy should be visible under Agents tab without refreshing when the fleet server is installed with a policy created from Add Fleet Server flyout.

Screen Recording:

https://user-images.githubusercontent.com/77374876/182537656-bf71c8ce-fdb7-4ac8-b3de-aee60f3cb301.mp4

elasticmachine commented 2 years ago

Pinging @elastic/fleet (Team:Fleet)

amolnater-qasource commented 2 years ago

@manishgupta-qasource Please review.

manishgupta-qasource commented 2 years ago

Secondary review for this ticket is Done

kpollich commented 1 year ago

@amolnater-qasource - Can we revalidate this against the new Fleet Server UIs? Closing for now.

amolnater-qasource commented 1 year ago

Hi @kpollich We have revalidated this issue on latest 8.6 SNAPSHOT and found the issue is still reproducible.

Observations:

Build details: BUILD: 58836 COMMIT: c735e9fc6fdf0221cc3134b5fe110e9ae4a0effb

Screen Recording:

https://user-images.githubusercontent.com/77374876/210537060-7d58e001-79cf-4dd3-b3d6-f6bb5444e3d4.mp4

https://user-images.githubusercontent.com/77374876/210537100-e87873d8-cf92-4380-a1db-f45ef4bc4908.mp4

https://user-images.githubusercontent.com/77374876/210537142-3cc32fac-f9e1-45c1-ad23-c793d0fe5337.mp4

Hence we are reopening this issue, as still reproducible. Thanks

amolnater-qasource commented 1 year ago

Hi Team,

We have revalidated this issue on latest 8.10.0 SNAPSHOT kibana cloud environment and found it still reproducible.

Observations:

Screen Recording:

Captures.zip

Build details: VERSION: 8.10.0 SNAPSHOT BUILD: 65561 COMMIT: 4dadcbb91136a3e7d39e4b419aa12e21a37e4918

Please let us know if anything else is required from our end.

Thanks!