-
Notifications
You must be signed in to change notification settings - Fork 89
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
[BUG] - Nebari-CLI returns an error when using DigitalOcean initialization #1840
Comments
Update: Digging through the stack trace, it appears that I have to set the AWS_SECRET_ACCESS_KEY value even though I chose DigitalOcean as the cloud provider. I did that and set the AWS_SECRET_ACCESS_KEY to some random string and was able to get past the error reported above. This feels like a bug, and probably should be fixed in the CLI. However, progressing through the rest of the init lets me reach the next error:
Translating the stack trace into English via ChatGPT, I get the following explanation:
Perhaps there may be a bug that results in |
@ericmjl Thanks for reporting, and I see this is your first issue - welcome! @iameskild Do you have thoughts on what's happening here? I'll try to reproduce as well. Related/relevant: #1344 |
Hi @ericmjl, thanks for raising this! Here is a description of the fix from my PR:
Let me know if you have any questions :) |
@iameskild are we able to run installs from M1 Macbooks now. I though that was broken? |
@dharhas deploying a cluster to one of the cloud providers works from Mac (M1 and otherwise) but |
Thanks for the quick fix, @iameskild! |
New user having the same problem. How do I fix that? |
Hi @fip17, sorry for the inconvenience. You can install nebari from the develop branch to get this latest fix
|
Describe the bug
Running the guided initialization results in an error. I have verified that I copied and pasted my token, ID, and access keys correctly.
Expected behavior
I expected the guided init to work without encountering the issues described above.
OS and architecture in which you are running Nebari
macOS Ventura 13.2.1 (22D68), M1 MacBook Air
How to Reproduce the problem?
Command output
Please see above error trace.
Versions and dependencies used.
Compute environment
None
Integrations
No response
Anything else?
I would label this low priority. I'm mostly test-driving this for personal use.
Tasks
The text was updated successfully, but these errors were encountered: