-
Notifications
You must be signed in to change notification settings - Fork 4.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
Changing flag for enhanced VPC routing from false to true on redshift serverless results in a validation exception #7507
Comments
Hi @meetvasu15 thanks for reaching out. I saw a similar issue here: hashicorp/terraform-provider-aws#26624. That error message you mentioned was also referenced in this comment where the user mentioned:
The comment below that one suggested a workaround, although I can't confirm if that works. But based on this information it seems like this issue could be on the Terraform side. If you believe the issue is with the CLI directly then please provide debug logs (with any sensitive info redacted) by adding |
Hi @tim-finnigan this is a different issue not really related to iam roles attribute hashicorp/terraform-provider-aws#26624 and I dont think its a terraform issue. The issue happens when I try to update a base_capacity or enhanced vpc routing flag along with an update to config-parameter using update-workgroup sub command.
This results in a validation exception, the expectation is that the update-workgroup subcommand should update the workgroup per arguments to the command. Attached debug logs. debug-workgroup-aws-cli.txt |
Thanks for following up - it seems like the issue may involve the underlying UpdateWorkgroup API then rather than directly the AWS CLI. I found an internal discussion where someone mentioned that |
As a work around deleting the workgroup and recreating it resolves the issue of updating the workgroup config - it is not the most convenient way to make updates. It forces us to have a downtime since multiple workgroups cannot be associated with a namespace, we will need to first delete the existing workgroup, VPCE and 53 alias record which takes a couple of minutes and then recreate a new one which also takes a couple of minutes. Is this issue being tracked anywhere else with the API team so that we can get updates? |
I'm not aware of an internal tracking issue for this but can try looking into it. Do you have an AWS Support plan? If so then we recommend opening a support case as that is a more direct way to escalate API issues to the appropriate team. |
Hi @tim-finnigan thanks for the response and the suggestion, I opened a support case with AWS. |
Thanks for following up. Please let us know here if you get any updates that may help others, and if any issue is found directly relating to the CLI then we can revisit this. I'll set this issue to auto-close after a few days if we don't hear back. |
Follow up from AWS
|
Describe the bug
When changing flag for enhanced VPC routing from false to true on redshift serverless workgroup using UpdateWorkgroup command, the request returns a validation exception "Can't update multiple configurations at the same time for workgroup [redacted]" even when the request was made with no changes in the existing config parameter values.
Expected Behavior
The CLI should update the enhancedVpcRouting flag.
Current Behavior
The CLI returns {"__type":"ValidationException","message":"Can't update multiple configurations at the same time for workgroup eng-datamart-compute."}
Reproduction Steps
Possible Solution
No response
Additional Information/Context
Existing config
UpdateWorkgroup request
CLI version used
2.9.3
Environment details (OS name and version, etc.)
Windows 10
The text was updated successfully, but these errors were encountered: