-
Notifications
You must be signed in to change notification settings - Fork 93
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] -TypeError: Object of type KeyValueDict is not JSON serializable #2819
Comments
I hacked around that particular issue by editing
Then used that to wrap the input to
That got me farther. However, it ended up failing later in the deployment process with a very similar issue:
|
Hi @mcg1969 , thanks for reporting this. For local deploys, we use Kind and test with it. Using K3s would be essentially the same as using an existing cluster, which is the least tested and documented part of Nebari. Could you validate that the local deploy with kind does work for you? That would let us narrow this down to the existing provider. Thanks! |
I was indeed using the |
@dcmcand Confirming: I do not encounter this with the AWS target. |
thanks @mcg1969, that is helpful. |
@mcg1969 I was able to reproduce this issue when deploying to k3s from 2024.7.1, but not from the current main branch. There may be other issues, but this error is not occurring. I believe this issue is related to #2767 and was likely fixed by #2797. We will have a new release here within a couple of days. Once the new release is out, can you retry? The traefik CRD's are still an issue, but that is essentially a new feature request, where this is a bug. |
Yes, happy to test. I totally understand about the other issue |
Describe the bug
Attempting to do a nebari deploy on an existing k3s cluster. I had a separate issue with the Traefik CRDs that I will raise separately. But once I get past that, I see this:
I hacked the
terraform.py
module to see what JSON was struggling with; it is this dictionary, with theKeyValueDict
objects.Those were generated by
nebari init
though! Here is theexisting
section of the config yaml:Expected behavior
It should make it through this stage without this error.
OS and architecture in which you are running Nebari
centos stream 8
How to Reproduce the problem?
installed a stock version of k3s. In order to get to this stage, I had to remove some of the Traefik CRDs that k3s installs for me, because they conflict with some that Terraform is trying to install. But once I let Terraform handle those, I was able to get to this point
Command output
The text was updated successfully, but these errors were encountered: