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

Error fetching Istio deployment status of the remote control plane in the Primary remote deployment #7053

Closed
matejnesuta opened this issue Jan 23, 2024 · 1 comment · Fixed by #7054
Assignees
Labels
backport completed Issue PRs have been backported backport needed Issue PRs require backport to versions specified in comments bug Something isn't working multicluster Related to multi cluster

Comments

@matejnesuta
Copy link
Contributor

Describe the bug

There is a 500 return code and an error notification for every refresh in Kiali.
image

Expected Behavior

No error notification about remote istio deployment status should be displayed to user, as this is the Primary remote setup

What are the steps to reproduce this bug?

I used the ./hack/run-integration-tests.sh --test-suite frontend-primary-remote -so true to run the Primary Remote with KinD

Environment

Kiali v1.80.0-SNAPSHOT (f648915)
Kiali Container v1.80.0-SNAPSHOT
Service Mesh Istio 1.20.2
Prometheus 2.41.0
Kubernetes v1.27.3

@matejnesuta matejnesuta added bug Something isn't working multicluster Related to multi cluster labels Jan 23, 2024
@nrfox nrfox self-assigned this Jan 23, 2024
@nrfox nrfox added the backport needed Issue PRs require backport to versions specified in comments label Jan 23, 2024
@nrfox
Copy link
Contributor

nrfox commented Jan 23, 2024

This will need to get backported to v1.79 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport completed Issue PRs have been backported backport needed Issue PRs require backport to versions specified in comments bug Something isn't working multicluster Related to multi cluster
Projects
Development

Successfully merging a pull request may close this issue.

3 participants