-
Notifications
You must be signed in to change notification settings - Fork 312
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
"ValueError: too many values to unpack" during 2.4.1 cluster creation #1241
Comments
Hi,
I simply removed the exception handling so that we should be able to see the stack trace on unexpected failures. Thanks, |
Thanks Francesco, here's the stack trace:
python --version: Python 3.7.3 |
aws#1241 Signed-off-by: Francesco De Martino <[email protected]>
Thanks, that really helped. Unfortunately there is a bug in the sanity check when a custom ec2_iam_role is specified in the config. For the moment you could set Here is the fix: #1246 |
aws#1241 Signed-off-by: Francesco De Martino <[email protected]>
Thanks, disabling the sanity checks will work for now! Still errored out as it looks like the IAM permission autoscaling:EnableMetricsCollection is now needed as part of 2.4.1 (didn't notice that in the release notes), but that's a separate issue. should be good to go after adding that to the policy. |
Hi @tgjohnst the EnableMetricsCollection has been added to the guide: Thank you |
#1241 Signed-off-by: Francesco De Martino <[email protected]>
I just updated to 2.4.1 and am now also experiencing the same ValueError during cluster creation as was referenced in #1236
Environment:
Bug description and how to reproduce:
Using the same template that worked fine in 2.4.0 (the only change being using 2.4.1 AMI), I now receive an error when running pcluster create
See cluster config attached:
pcluster_config_RCE.txt
Any idea why 2.4.1 is now throwing this error?
The text was updated successfully, but these errors were encountered: