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

Unhelpful 404 error for missing API resources #949

Open
nightkr opened this issue Jul 6, 2022 Discussed in #948 · 2 comments
Open

Unhelpful 404 error for missing API resources #949

nightkr opened this issue Jul 6, 2022 Discussed in #948 · 2 comments
Labels
ergonomics ergonomics of the public interface errors error handling or error ergonomics good first issue Good for newcomers

Comments

@nightkr
Copy link
Member

nightkr commented Jul 6, 2022

Discussed in #948

Originally posted by jesperpedersen July 6, 2022
Hi,

I'm currently looking at

2022-07-06T08:48:38.812069629-04:00 WARN kube_client::client - Unsuccessful data error parse: 404 page not found
2022-07-06T08:48:38.812085204-04:00 TRACE want - signal: Want
2022-07-06T08:48:38.812127318-04:00 DEBUG kube_client::client - Unsuccessful: ErrorResponse { status: "404 Not Found", message: "\"404 page not found\\n\"", reason: "Failed to parse error data", code: 404 } (reconstruct)

which is from the /apiserver - but is there a way to get more information on this ? Like is it a missing endpoint (resource) or are credentials to blame.

Getting the full URL plus user info into the DEBUG message would be great.

Thanks for any help in advance !

@nightkr nightkr changed the title 404 Page Not Found Unhelpful 404 error for missing API resources Jul 6, 2022
@nightkr nightkr added bug Something isn't working errors error handling or error ergonomics good first issue Good for newcomers ergonomics ergonomics of the public interface and removed bug Something isn't working labels Jul 6, 2022
@jesperpedersen
Copy link

2022-07-06T09:35:35.550561233-04:00 DEBUG kube_client::client - Unsuccessful: ErrorResponse { status: "Failure", message: "the server could not find the requested resource", reason: "NotFound", code: 404 }

@Stef16Robbe
Copy link

Hi all, I'm new to Rust and I would like to help out by picking this ticket up 😄. I have two questions:

  1. Should the URI be only displayed in the DEBUG message or also in the Error message?
  2. What is exactly meant with "plus user info"?

Currently I have something like this:

2024-08-04T10:49:29.815278Z DEBUG kube_client::client: Unsuccessful: ErrorResponse { status: "404 Not Found", message: "\"404 page not found\\n\"", reason: "Failed to parse error data", code: 404 }, uri: /apis/chaos-mesh.org/v1alpha1/namespaces/default/podnetworkchaos/notfound (reconstruct)
Error: Api(ErrorResponse { status: "404 Not Found", message: "\"404 page not found\\n\"", reason: "Failed to parse error data", code: 404 })

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ergonomics ergonomics of the public interface errors error handling or error ergonomics good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants