Hello,
I have a TAO API instance installed on an Openshift 4.16 cluster running CoreOS with two L40 cards. I installed it using the helm chart available from the NGC Catalog website.
Pods are working, I was able to run jupyterlab, service tao api also supports api call to ingress paths.
Unfortunately I can’t log in via api to service tao.
Using the ngc key thanks to which I downloaded tao from ngc registry, I now receive error 401 - invalid key
The following shows the code running from pod jupyterlab on opneshift cluster
host_url = “http://tao-toolkit-api-service.tao-toolkit.svc.cluster.local:8000” #pod service name
ngc_api_key = “api_key”
data = json.dumps({“ngc_api_key”: ngc_api_key})
response = requests.post(f“{host_url}/api/v1/login”, data=data)
print(response)
<Response [401]>.
Same error I have when I run curl from another pod in cluster
~$ BASE_URL=http://tao-toolkit-api-service.tao-toolkit.svc.cluster.local:8000/api/v1
~ $ NGC_API_KEY=ngc-api-key
~ $ curl -s -X POST $BASE_URL/login -d ‘{"ngc_api_key: “’“$NGC_API_KEY”‘"}’
{ “error_code”:1, “error_desc”: “Unauthorized: Credentials error: Invalid NGC_API_KEY"}
Error in tao-api-app pod is Unauthorized: Credentials error: Invalid NGC_API_KEY
127.0.0.1 - - [13/Mar/2025:11:44:19 +0000] “POST /api/v1/login HTTP/1.1” 401 295 “-” “curl/8.12.1”
Other api calls work fine
curl -s -X GET http://tao-toolkit-api-service.tao-toolkit.svc.cluster.local:8000/version
{“branch”:“release/5.5.0”,“sha”:“35b72ba9dcae2dee704b0279a7d3a97375e87450”,“time”:“20240808T170704Z”,“version”:“5.5.0”}
I wonder if the problem is on the API side or a bug on the deployment side on openshift.
I checked carefully the accuracy of the pasted ngc key with nvapi prefix as well as without.
Regards
2 posts - 2 participants