S3 Backup may fail after upgrade to v2.6 with the error "Error - Workers could not be launched"
S3 Backup may fail after upgrade to v2.6 with the error "Error - Workers could not be launched".
This issue may happen if subnet is set to "Any" in the worker configuration.
The following errors may be logged in the Backup Log:Info - Starting copy to S3
Error - Failed to launch worker in region US East (N. Virginia)
Error - Workers could not be launched
Error - Backup copy failed
The following errors may be logged in the CPM Server logs:
ERROR: launch_instance(worker_utils.py:98) Failed to launch instance
Traceback (most recent call last):
File "./cpmserver/cpm/workers/worker_utils.py", line 89, in launch_instance
File "./common/aws_utils.py", line 1626, in call_boto_with_retry
ClientError: An error occurred (InvalidParameter) when calling the RunInstances operation: Security group sg-12345678 and subnet subnet-98765432 belong to different networks.
ERROR: launch_worker(worker_utils.py:361) Failed to launch worker instance