You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Deploy a isvc
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:
Screenshots
I created a example isvc using the mnist model
Upon sending a request to the route /v2/models/${MODEL_ID} (/v2/models/mnist-isvc), I received the following error message:
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.
The text was updated successfully, but these errors were encountered:
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.
To Reproduce
Steps to reproduce the behavior:
isvc
modelmesh-serving
service and send request to the routev2/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:
Screenshots
I created a example isvc using the mnist model
Upon sending a request to the route
/v2/models/${MODEL_ID}
(/v2/models/mnist-isvc
), I received the following error message:Environment (please complete the following information):
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.
The text was updated successfully, but these errors were encountered: