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
I would like to enable gRPC inferencing with modelmesh. When I follow instructions [1] and [2], I am able to do successful grpcurl request. However, I noticed that the rest-proxy container starts failing.
To Reproduce
Steps to reproduce the behavior:
Install modelmesh in a specific namespace (opendatahub in my case)
Create secret (ie. mm-new) following the prompts here. Inferencing namespace name is modelmesh-serving. Apply the secret:
Go to Pods and select the modelmesh-serving-ovms-1.x-* pod and go to rest-proxy logs. This is what it shows:
{"level":"info","ts":"2023-07-10T15:31:14Z","msg":"Starting REST Proxy..."}
{"level":"info","ts":"2023-07-10T15:31:14Z","msg":"Using TLS"}
{"level":"info","ts":"2023-07-10T15:31:14Z","msg":"Registering gRPC Inference Service Handler","Host":"localhost","Port":8033,"MaxCallRecvMsgSize":16777216}
{"level":"info","ts":"2023-07-10T15:31:19Z","msg":"Listening on port 8008 with TLS"}
2023/07/10 15:31:23 http: TLS handshake error from <IP1>:50510: read tcp <IP3>:8008-><IP1>:50510: read: connection reset by peer
2023/07/10 15:31:23 http: TLS handshake error from <IP2>:47526: read tcp <IP3>:8008-><IP2>:47526: read: connection reset by peer
2023/07/10 15:31:28 http: TLS handshake error from <IP1>:50518: read tcp <IP3>:8008-><IP1>:50518: read: connection reset by peer
Error continues in repeating fashion until inference service is deleted (which deletes the serving runtime pod as well).
Interestingly, if one goes to the other pod (replicaSet is set to 2) and checks the rest-proxy logs, it has no error:
{"level":"info","ts":"2023-07-10T13:20:00Z","msg":"Starting REST Proxy..."}
{"level":"info","ts":"2023-07-10T13:20:00Z","msg":"Using TLS"}
{"level":"info","ts":"2023-07-10T13:20:00Z","msg":"Registering gRPC Inference Service Handler","Host":"localhost","Port":8033,"MaxCallRecvMsgSize":16777216}
{"level":"info","ts":"2023-07-10T13:20:05Z","msg":"Listening on port 8008 with TLS"}
For reference, sharing the runtime Deployment yaml:
All other logs are fine including the ones in modelmesh-controller.
Expected behavior
Rest-proxy container isn't showing failing logs.
Screenshots
Environment (please complete the following information):
OpenShift 4.13.0
Open Data Hub 1.7.0
Modelmesh version: v0.11.0-alpha (ref)
Controller namespace: opendatahub
User/isvc namespace: modelmesh-serving
Additional context
We tried deploying isvc in several namespaces and try the grpc inferencing once and it failed. We found that gRPC inferencing works only in one namespace. We have tried only once but I will give it a shot again. That's potentially next connected issue.
The text was updated successfully, but these errors were encountered:
I experimented with the TLS setup on plain Kubernetes and OpenShift. Looks like we need to update our TLS doc to make it work.
Although I did not fully replicate your setup, I was able to get TLS setup without any errors showing in any of the rest-proxy containers across two namespaces after following our FVT setup for TLS. The instructions do the same with OpenSSL need to be updated however.
Describe the bug
I would like to enable gRPC inferencing with modelmesh. When I follow instructions [1] and [2], I am able to do successful grpcurl request. However, I noticed that the
rest-proxy
container starts failing.To Reproduce
Steps to reproduce the behavior:
opendatahub
in my case)mm-new
) following the prompts here. Inferencing namespace name ismodelmesh-serving
. Apply the secret:modelmesh-serving
in my case)Inference service:
Status of isvc after is:
Status of the route:
modelmesh-serving-ovms-1.x-*
pod and go torest-proxy
logs. This is what it shows:Error continues in repeating fashion until inference service is deleted (which deletes the serving runtime pod as well).
Interestingly, if one goes to the other pod (replicaSet is set to 2) and checks the
rest-proxy
logs, it has no error:For reference, sharing the runtime Deployment yaml:
All other logs are fine including the ones in modelmesh-controller.
Expected behavior
Rest-proxy container isn't showing failing logs.
Screenshots
Environment (please complete the following information):
OpenShift 4.13.0
Open Data Hub 1.7.0
Modelmesh version: v0.11.0-alpha (ref)
Controller namespace:
opendatahub
User/isvc namespace:
modelmesh-serving
Additional context
We tried deploying isvc in several namespaces and try the grpc inferencing once and it failed. We found that gRPC inferencing works only in one namespace. We have tried only once but I will give it a shot again. That's potentially next connected issue.
The text was updated successfully, but these errors were encountered: