Skip to content

(2026.03 and earlier) Fail to list project owners and members in the user drop‐down when sharing a Virtual Desktop

Jump to bottom
Julian Allende Russek edited this page Jul 9, 2026 · 4 revisions

Bug description

When sharing a desktop with other users, the user selection drop-down appears empty. This occurs due to a front-end bug where the project associated with the desktop has only individual users assigned and no groups attached.

Affected versions

2026.03 and earlier

Mitigation

For 2025.06 and 2025.09:

  1. Download patch.py and session_permissions_project_users.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
    2. The patch script requires AWS CLI v2, Python 3.9.16, 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 created by RES.
    4.  OUTPUT_DIRECTORY=<output-directory>
 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/session_permissions_project_users.patch --output ${OUTPUT_DIRECTORY}/session_permissions_project_users.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 cluster-manager --patch ${OUTPUT_DIRECTORY}/session_permissions_project_users.patch`

  3. Restart the Cluster Manger instance for your environment. You may also terminate the instance from the Amazon EC2 Management Console.

    1.  INSTANCE_ID=$(aws ec2 describe-instances \
             --filters \
             Name=tag:Name,Values=${ENVIRONMENT_NAME}-cluster-manager \
             Name=tag:res:EnvironmentName,Values=${ENVIRONMENT_NAME}\
             --query "Reservations[0].Instances[0].InstanceId" \
             --output text)
 
 aws ec2 terminate-instances --instance-ids ${INSTANCE_ID}

  4. Verify the new Cluster Manager instance status by checking the activity of the auto scaling group starting with the name cluster-manager-asg. Wait until the new instance is launched successfully.

For 2025.12 and 2026.03:

  1. Create an S3 bucket with ACLs disabled.
  2. Download patch_host.py and idea-cluster-manager-{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, 2025.12.01, or 2026.03 in the command below, and <partition> with Classic or GovCloud :
    1. The patch applies to 2025.12, 2025.12.01, 2026.03
    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 <bucket-name>.
    4.  OUTPUT_DIRECTORY=<output-directory>
 ENVIRONMENT_NAME=<environment-name>
 RES_VERSION=<RES_VERSION>
 BUCKET_NAME=<bucket-name>
 PARTITION=<partition>
 
 mkdir -p ${OUTPUT_DIRECTORY}
 HASH=$(case $RES_VERSION in "2026.03") echo 52a634f2;; "2025.12.01") echo 6eb18433;; "2025.12") echo 4905bb84;; 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-cluster-manager-${RES_VERSION}-${HASH}.tar.gz --output ${OUTPUT_DIRECTORY}/idea-cluster-manager-${RES_VERSION}-${HASH}.tar.gz
  3. Run the following patch command: 
    1.  python3 ${OUTPUT_DIRECTORY}/patch_host.py --environment-name ${ENVIRONMENT_NAME} --module cluster-manager --zip-file ${OUTPUT_DIRECTORY}/idea-cluster-manager-${RES_VERSION}-${HASH}.tar.gz --s3-bucket ${BUCKET_NAME} --partition ${PARTITION}
  4. Restart the Cluster Manger instance for your environment. You may also terminate the instance from the Amazon EC2 Management Console. 
    1.  INSTANCE_ID=$(aws ec2 describe-instances \
             --filters \
             Name=tag:Name,Values=${ENVIRONMENT_NAME}-cluster-manager \
             Name=tag:res:EnvironmentName,Values=${ENVIRONMENT_NAME}\
             --query "Reservations[0].Instances[0].InstanceId" \
             --output text)
 
 aws ec2 terminate-instances --instance-ids ${INSTANCE_ID}
  5. Verify the new Cluster Manager instance status by checking the activity of the auto scaling group starting with the name cluster-manager-asg. Wait until the new instance is launched successfully.

Clone this wiki locally
⌂ 换网址