You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running kitchen converge or test with --concurrency greater than 10, one or more of the VMs will usually not be created. When I try the same concurrency with kitchen create, I get this exception:
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Request limit exceeded.]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration
I have a workaround which I think also proves the problem: In my Thorfile I have separated the destroy/create/converge/verify/destroy steps into separate commands, and run the create and destroy steps with --concurrency=10, with the rest at full concurrency.
I'm running 15 suites concurrently, with one of the instances having an extra EBS volume.
I don't know if this issue belongs here, or in the test-kitchen project itself.
Thanks,
-Bryce.
The text was updated successfully, but these errors were encountered:
When running kitchen converge or test with --concurrency greater than 10, one or more of the VMs will usually not be created. When I try the same concurrency with kitchen create, I get this exception:
I have a workaround which I think also proves the problem: In my Thorfile I have separated the destroy/create/converge/verify/destroy steps into separate commands, and run the create and destroy steps with --concurrency=10, with the rest at full concurrency.
I'm running 15 suites concurrently, with one of the instances having an extra EBS volume.
I don't know if this issue belongs here, or in the test-kitchen project itself.
Thanks,
-Bryce.
The text was updated successfully, but these errors were encountered: