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

Kubernetes: Issue: Errors: Request failed with 500 , {"error":"Unknown suffix: u"} #9740

Closed
hsparmar1 opened this issue Feb 22, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@hsparmar1
Copy link

Expected Behavior

The user should be able to click on the the Kubernetes tab in the Component Page and have the Your Cluster display the Kubernetes information about the Component: Deployment, Ingress, and Service, without seeing the following error:

"There was a problem retrieving some Kubernetes resources for the entity: some-service-in-k8s. This could mean that the Error Reporting card is not completely accurate." Errors: Request failed with 500 , {"error":"Unknown suffix: u"}

Actual Behavior

The Kubernetes tab in the Component Page intermittently displays the following error:

"There was a problem retrieving some Kubernetes resources for the entity: some-service-in-k8s. This could mean that the Error Reporting card is not completely accurate." Errors: Request failed with 500 , {"error":"Unknown suffix: u"}

This error sometimes occurs right after entering the Kubernetes Tab, in which case, nothing else displays on the page except this error. After 30 seconds or so the error disappears, and the Kubernetes Tab will display the correct Your Cluster display with data from Kubernetes about the Component.

Other times, the error will not display for 30 seconds or so. After which time, the error will display and remain on the Kubernetes tab along with all the Kubernetes data: Deployment, Ingress, and Service, about the Component.

Steps to Reproduce

  1. Sign into Backstage Home
  2. Select Component that has a Kubernetes Deployment object, and the Backstage Annotation to Kubernetes Label mapping.
  3. Navigate to Kubernetes Tab. The error may appear right away; or, it may appear after 30 seconds or so.

Context

This error is mostly a nuisance, but the team here would like to have it investigated just in case it is responsible for more serious issues.

Your Environment

  • Browser Information: Chrome Version 98.0.4758.102 (Official Build) (x86_64)

  • Output of yarn backstage-cli info:

yarn run v1.22.1
$ /Users/Harjeet.S.Parmar/Development/qsid-dev/backstage/backstage-plugins-devel/node_modules/.bin/backstage-cli info
OS:   Darwin 21.2.0 - darwin/x64
node: v14.19.0
yarn: 1.22.1
cli:  0.13.2 (local)

Dependencies:
  @backstage/core-plugin-api 0.4.1
✨  Done in 2.93s.
  • Backstage: Deployed on EKS single Pod
@hsparmar1 hsparmar1 added the bug Something isn't working label Feb 22, 2022
@freben
Copy link
Member

freben commented Feb 24, 2022

@mclarke47 Is this something that rings a bell?

@Rugvip
Copy link
Member

Rugvip commented Mar 2, 2022

Hi! I wanna check if this is something that is still happening if you upgrade to the most recent release?

@mclarke47
Copy link
Collaborator

If this is still happening it might be fixed by upgrading the JS K8S lib kubernetes-client/javascript#757

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@benjdlambert
Copy link
Member

Closing as should be fixed in the merged PR, let's test and feel free to re-open if still an issue after release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants