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

Data Plane API Error - "Not Found" when Retrieving Model Metadata #418

Closed
anhquan075 opened this issue Aug 14, 2023 · 1 comment · Fixed by kserve/rest-proxy#26
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@anhquan075
Copy link

Describe the bug

When I try to use the Kserve Data Plane API in ModelMesh Serving to get the model metadata, an error with the code 5 and message "Not Found" is encountered.

{"code":5, "message":"Not Found"}

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a isvc
  2. Port forward the modelmesh-serving service and send request to the route v2/models/${MODEL_NAME}[/versions/${MODEL_VERSION}]

Expected behavior

The expected behavior is to receive a response similar to Kserve in here with the following format:

$metadata_model_response =
{
  "name" : $string,
  "versions" : [ $string, ... ] #optional,
  "platform" : $string,
  "inputs" : [ $metadata_tensor, ... ],
  "outputs" : [ $metadata_tensor, ... ]
}

Screenshots
I created a example isvc using the mnist model
image
Upon sending a request to the route /v2/models/${MODEL_ID} (/v2/models/mnist-isvc), I received the following error message:image

Environment (please complete the following information):

  • OS: MacOS Monterey 12.6

Additional context
Are there any guides or suggestions available to help resolve this issue? My task requires retrieving model metadata such as input/output names and shapes.

@anhquan075 anhquan075 added the bug Something isn't working label Aug 14, 2023
@rafvasq rafvasq self-assigned this Aug 15, 2023
@njhill
Copy link
Member

njhill commented Aug 16, 2023

This needs to be added to the rest-proxy, see kserve/rest-proxy#14

@ckadner ckadner added this to the v0.11.1 milestone Sep 26, 2023
@ckadner ckadner linked a pull request Oct 2, 2023 that will close this issue
spolti pushed a commit to spolti/rest-proxy that referenced this issue Jan 10, 2024
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

Successfully merging a pull request may close this issue.

4 participants