(2025.12.01 and earlier) VDI fails to create DCV session when resuming from stopped state

[Murielxun]

Bug description

When a VDI is resumed from a stopped state, it may fail to resume and enter an ERROR state. SSM commands for recreating the DCV session show the error: Could not create session. The dcvserver service is not running.

Affected versions

2025.12.01 and earlier

Mitigation

The patch only applies to newly launched VDIs.

For 2025.06 and 2025.09:

1. Download patch.py and check_dcv_server_ready.patch for version 2025.06, 2025.06.01, or 2025.09 by replacing <output-directory> with the directory to download the patch script and patch file and <environment-name> with the name of your RES environment in the command below:
   1. The patch applies to RES 2025.06, 2025.06.01, or 2025.09

   1. The patch script requires AWS CLI v2, Python 3.9.16, and Boto3.
   2. Configure the AWS CLI for the account / region where RES is deployed, and make sure that you have S3 permissions to write to the bucket created by RES.

   3.  ENVIRONMENT_NAME=<environment-name>
       RES_VERSION=<res-version> # e.g. 2025.06, 2025.06.01, or 2025.09
       
       mkdir -p ${OUTPUT_DIRECTORY}
       curl https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patch.py --output ${OUTPUT_DIRECTORY}/patch.py
       curl https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patches/check_dcv_server_ready.patch --output ${OUTPUT_DIRECTORY}/check_dcv_server_ready.patch
      

2. Navigate to the directory where the patch script and patch file are downloaded. Run the following patch command:

   1. python3 ${OUTPUT_DIRECTORY}/patch.py --environment-name ${ENVIRONMENT_NAME} --res-version ${RES_VERSION} --module virtual-desktop --patch ${OUTPUT_DIRECTORY}/check_dcv_server_ready.patch

3. Launch a new VDI, stop it, and then resume it with the fix.

For 2025.12 and 2026.03:

1. Create a S3 bucket with ACLs disabled.
2. Download patch_host.py and idea-virtual-desktop-{res-version}-*.tar.gz by replacing <output-directory> with the directory to download the patch script, <environment-name> with the name of your RES environment, <bucket-name> with the name of a ACLs disabled S3 bucket under the account/region where RES is deployed, RES_VERSION with 2025.12 or 2025.12.01, and <partition> with Classic or GovCloud in the command below:
   1. The patch applies to 2025.12 or 2025.12.01
   2. The patch script requires AWS CLI v2, Python 3.9.16 or above, and Boto3.
   3. Configure the AWS CLI for the account / region where RES is deployed, and make sure that you have S3 permissions to write to the bucket provided through .

   4.  ENVIRONMENT_NAME=<environment-name>
       RES_VERSION=<RES_VERSION>
       BUCKET_NAME=<bucket-name>
       PARTITION=<partition>
       
       mkdir -p ${OUTPUT_DIRECTORY}
       HASH=$(case $RES_VERSION in "2025.12.01") echo c3afeeb6;; "2025.12") echo 3f05fda1;; esac)
       curl https://research-engineering-studio-us-east-1.s3.us-east-1.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patch_host.py --output ${OUTPUT_DIRECTORY}/patch_host.py
       curl https://research-engineering-studio-us-east-1.s3.us-east-1.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patches/idea-virtual-desktop-${RES_VERSION}-${HASH}.tar.gz --output ${OUTPUT_DIRECTORY}/idea-virtual-desktop-${RES_VERSION}-${HASH}.tar.gz
      

3. Run the following patch command:
   1. python3 ${OUTPUT_DIRECTORY}/patch_host.py --environment-name ${ENVIRONMENT_NAME} --module virtual-desktop --zip-file ${OUTPUT_DIRECTORY}/idea-virtual-desktop-${RES_VERSION}-${HASH}.tar.gz --s3-bucket ${BUCKET_NAME} --partition ${PARTITION}
4. Launch a new VDI, stop it, and then resume it with the fix.