Loading indicator are hanged and not processing.

[dikshachauhan-qasource]

Kibana version: 7.14 Snapshot Kibana Cloud-qa environment

Host OS and Browser version: Chrome, Firefox and edge

Preconditions:

1. 7.14 Snapshot Kibana Cloud-qa environment should be available.

Build Details:

BUILD 42091
COMMIT fe3ea8ed1fc80caa3acd805d24a1e9ea882aa30f

Steps to reproduce:

• Login to Kibana.
• Navigate to Admin tab.
• Look for loading indicators.
• Navigate to integrations tab.
• select and open any integration.
• Observe, the loading indicators are stuck.

Expected result:

• Loading indicators should be in processing mode.

Recording: https://user-images.githubusercontent.com/72375798/123781999-7a459d80-d8f2-11eb-9d6e-de3f9fcfd3f7.mp4

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[dikshachauhan-qasource]

@manishgupta-qasource Please review

[manishgupta-qasource]

Reviewed & assigned to @jen-huang

[EricDavisX]

@dikshachauhan-qasource can you add a screenshot or video showing?

[jen-huang]

@EricDavisX There is a video at the bottom :D

Actually I just tested this with a new 7.14-SNAPSHOT deployment and am not seeing the same thing, the spinners animate fine for me. @dikshachauhan-qasource can you click around other areas of Kibana and observe the animation (or lack thereof) in them? From the video it seems like a resource or performance problem of your machine or VM, and not a Fleet problem, for example the spinner that replace the Elastic logo in the very top left of the page also does not animate. What is the browser you are using?

I'm closing this for now.

[dikshachauhan-qasource]

Hi @jen-huang

We have retested it with 7.14BC1 cloud-qa build and found it still reproducible on all the browsers. Hence reopening.

Build details:

BUILD 42292
COMMIT 071a74e02f82b79a4a10026b5c9e02d593112fd4

Recording: https://user-images.githubusercontent.com/72375798/124469502-102c6d00-ddb8-11eb-8d9d-b4e4ee6e8fd3.mp4

Thanks QAS

[jen-huang]

@dikshachauhan-qasource From your recording it seems that this is not a Fleet-specific problem (observed the same in Endpoint). I still haven't been able to reproduce on my end. Can you or @manishgupta-qasource try a different machine?

[amolnater-qasource]

Hi @jen-huang We have revalidated this with 7.14.0 Snapshot Kibana Cloud environment and found it still reproducible. We have also attempted on various Windows VMs to re-confirm this issue, it was reproducible there as well.

Build details:

Build: 42333
Commit: d2904ca073e91582a2c5fa6ef6e712491cf3521f

Screen Recording:

https://user-images.githubusercontent.com/77374876/124744574-8954cd00-df3c-11eb-9409-e9c181416ca9.mp4

Thanks QAS

[jen-huang]

@amolnater-qasource Can you try it in a different physical machine that is not in a VM? I still feel like it is a resource constraint issue.

[amolnater-qasource]

Hi @jen-huang We have validated this on our physical/hardware machines and this issue is consistently reproducible from the reported day. Out of 5 hardware machines this issue was reproducible on 4 of them. Further we tried to clear cache and tested on browser private mode. It is still reproducible there.

System specifications: Windows 10 x64 bits i7 processor Ram: 8 GB4 Screen Resolution: 1366x768

Thanks QAS

[EricDavisX]

@amolnater-qasource can you re-test this with 7.14 GA please? We may end up leaving it low impact or closing as won't fix - but it is good to acknowledge it is reproducible or not as part of reassessing. so i have re-opened it

[dikshachauhan-qasource]

Hi @EricDavisX

We have validated this issue on shipped 7.14 Prod Kibana build and found it still reproducible on our Windows 10 OS machine on all browsers[used cognito windows].

Thanks QAS

[jen-huang]

@EricDavisX Can you spend some time diving into this when you have time? I had closed this initially because the videos shows a Kibana-wide issue (not just in Fleet and Integrations) which still points to a system issue to me as we have not seen reports from other QA areas.

[EricDavisX]

I never made time for this, apologies. @dikshachauhan-qasource if you want to follow though, the right path is to confirm as Jen notes that the problem is not specific to Fleet and to ensure this isn't logged elsewhere for general-Kibana side. If it is indeed not, we can remove Fleet labels and pass it to the general Kibana team for review .

[dikshachauhan-qasource]

Hi @EricDavisX

This issue is still noticeable on our machines. So we are tagging Kibana team for review.

Thanks QAS

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)