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

Local Konveyor UI fails to load when running on Minikube #2110

Open
EstyBiton opened this issue Sep 26, 2024 · 1 comment
Open

Local Konveyor UI fails to load when running on Minikube #2110

EstyBiton opened this issue Sep 26, 2024 · 1 comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@EstyBiton
Copy link

Environment:

  • Minikube version: v1.33.1
  • Installation guide: WSL Installation Guide
  • Operating System: Windows
  • Browser: Chrome version 128.0.6613.138

Issue Description:
Following the installation of Konveyor on Minikube using the provided guide, the local Konveyor UI is inaccessible.
The following issues are observed:

  1. UI Connection Error:
    The Konveyor UI displays an "Unable to connect" error message, stating:
    "There was an error retrieving data. Check your connection and try again."
  2. API Connection Errors:
    The browser's developer console logs multiple failed API requests:
    These requests result in AxiosError with the message "Request failed with status code 504".

Steps to Reproduce:

  1. Install Konveyor on Minikube following the WSL Installation Guide.
  2. Attempt to access the Konveyor UI via the local URL.
  3. Inspect the browser's developer tools console for errors.

Expected Behavior:
The Konveyor UI should load successfully, displaying the application interface and data.

Actual Behavior:

  • The UI fails to load, presenting a connection error.
  • The console reveals multiple API request timeouts.

Additional Information:

  • The issue persists across multiple access attempts.
  • No specific error messages are visible in the Minikube or Konveyor logs indicating the root cause.

Screenshots:
UI Connection Error:
Image

API Connection Errors:
Image

@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 26, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. label Sep 26, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Sep 26, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant