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] Integrations UI not loading when EPR is inaccessible #133514

Closed
juliaElastic opened this issue Jun 3, 2022 · 3 comments
Closed

[Fleet] Integrations UI not loading when EPR is inaccessible #133514

juliaElastic opened this issue Jun 3, 2022 · 3 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team v8.3.0

Comments

@juliaElastic
Copy link
Contributor

Integrations UI not loading when EPR is inaccessible
Version: 8.3

Seems to be a regression since this was working since 8.0 #115564

Steps to reproduce:

  • Set EPR to a dummy value in kibana.yml, e.g. xpack.fleet.registryUrl: http://localhost:12345
  • Visit Integrations app
  • Result: Installed integrations are not loading, neither Browse or Installed tabs, fails with 502 after 2 minutes.
  • Expected: Page should load with a callout, installed integrations should show installed cards.

image

@juliaElastic juliaElastic added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team v8.3.0 labels Jun 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@juliaElastic juliaElastic changed the title Integrations UI not loading when EPR is inaccessible [Fleet] Integrations UI not loading when EPR is inaccessible Jun 3, 2022
@juliaElastic juliaElastic self-assigned this Jun 3, 2022
@juliaElastic
Copy link
Contributor Author

After further investigation, I found that the callout is visible and the epr call times out after 30s when I make EPR inaccessible by editing the /etc/hosts file as it was tested here.

So it is not a regression per se, but a different way of setting an inaccessible epr.

image

@juliaElastic juliaElastic changed the title [Fleet] Integrations UI not loading when EPR is inaccessible [Fleet] Integrations UI not loading when registryUrl is inaccessible Jun 3, 2022
@juliaElastic juliaElastic changed the title [Fleet] Integrations UI not loading when registryUrl is inaccessible [Fleet] Integrations UI not loading when EPR is inaccessible Jun 3, 2022
@juliaElastic
Copy link
Contributor Author

juliaElastic commented Jun 3, 2022

I don't know what happened, but I can't reproduce this now. I see the callout coming up after 30s in both ECE and local.

I think the 2 min timeout was coming when all network access was blocked, not only EPR.
EDIT: Yes, I tested again with the whole network blocked, and I got the 2 min timeout. The callout is still visible, so that is working fine. I think I got confused because I took a screenshot of the Installed tab, which doesn't show the callout.

The installed packages are not showing the installed bundled packages though, I think that is expected based on this discussion #74614 (comment)

with epr inaccessible:

{"statusCode":502,"error":"Bad Gateway","message":"Error connecting to package registry: request to http://localhost:12345/categories?experimental=true&include_policy_templates=true&kibana.version=8.4.0 failed, reason: connect ECONNREFUSED 127.0.0.1:12345"}

image

with no internet access:

{"ok":false,"message":"backend closed connection"}

image

@juliaElastic juliaElastic reopened this Jun 3, 2022
@juliaElastic juliaElastic closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 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 Team:Fleet Team label for Observability Data Collection Fleet team v8.3.0
Projects
None yet
Development

No branches or pull requests

2 participants