-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Cvat helmchart on kubernetes v.2.14.4 not working with s3 cloudstorage. #8108
Comments
Could you post the output of the describe command for one of |
Name: cvat-utv-backend-server-6c76b859f5-5bmdw |
You need to set SMOKESCREEN_OPTS to add allow rule for your s3 cidr Please see the PR description for more details |
It seems like the linked PR was merged back in 2.5 whereas I had no issues connecting it in 2.12.1. It would seem to be that it's unlikely this could be the cause of the issues mentioned. |
I didn't say the PR mentioned was causing this behavior, the description at the link gives the solution, but if you need to know the PR that causes this for onperm s3 f234693 |
I have tried to set smokecreen_opts value to 'false' but i still get the same error.. Am i suposed to make a list of all the enpointurls that are accepted or can i disable the smokescreen and accept all? |
'false' is not valid option, |
Actions before raising this issue
Steps to Reproduce
I recently uppdated cvat from 2.10.2 to 2.14.4. The uppdate has gone well in general with all the pods are up and running. But when i try to attach a on prem s3 to cvat using the cloud storage and it gives me this error: "Failed to connect to proxy URL: "http://localhost:4750". I don't know why it's trying to connect to a proxy, i have dubblechecked all the secret and access keys which worked fine before the update. I dont know if its some issues with the new image or something.
Expected Behavior
I expect it would attach the s3 storage as it did on v.2.10.2
Possible Solution
No response
Context
No response
Environment
The text was updated successfully, but these errors were encountered: