-
Notifications
You must be signed in to change notification settings - Fork 329
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
Unable to add a Cloud backend #1412
Comments
@rajesh1084 seems like all the strato (multicloud) docker containers have not come up properly. The Backend types API call seems to be failing. Could you try the following and post the screenshots here:
If the installation was interrupted in between, or if you have shutdown the system and restarted this issue may arise. |
Sure @anvithks , I will post those details in a while.
|
typo: seems like all the strato (multicloud) docker containers have not come up properly |
Closing this issue as I am able to bring up strato on a different setup and able to see the cloud backends. |
That's great @rajesh1084. Let me know if you face any other issues. |
While it lists a set of cloud backends, when we try to register an AWS S3 bucket, it's failing -
|
@rajesh1084 Seems like the backend information provided may be incorrect. Have you generated the AK/SK in SODA Dashboard? |
No, we haven't generated AK/SK in the dashboard; but using the AK/SK of our AWS a/c.
Yes. We did set Following this documentation trying with the following values: Any pointers? |
Issue/Feature Description:
Deployed Soda multi-cloud as per the instructions in the documentation. Enabled all the required projects and parameters in the yaml files.
However, in the UI, when I try to register a new cloud backend, the drop-down doesn't show up any values. Refer to the screenshot.
Why this issue to fixed / feature is needed(give scenarios or use cases):
How to reproduce, in case of a bug:
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)
Soda was deployed on a single VM (Ubuntu 20.04.4 LTS)
The text was updated successfully, but these errors were encountered: