1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Thanks for writing to re:Post.
Looking at the issue, it seems to be a syntax error due to which the step-concurrency-level parameter was unidentified during cluster launch through CLI.
The error is reproducible when a comma is inserted between the parameter and the value (--step-concurrency-level,10).
It can be resolved by replacing comma with a space (--step-concurrency-level 10) in create-cluster CLI command.
Relevant content
- asked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago