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
The Guacamole Windows VM bundle in #5048 maps the default 2 CPU | 8GB RAM option to Standard_D2s_v7. Azure rejected that size in the switzerlandnorth CI environment, causing the extended Guacamole test to fail when creating its Windows VM.
The bundle already exists at templates/workspace_services/guacamole/user_resources/guacamole-azure-windowsvm/porter.yaml. Commit 2264adeb in #5048 changes its four size mappings from v6 to v7. At the time of filing, #5048 is still open and main uses v6. This report tracks a separate follow-up fix intended to merge after #5048.
Evidence
Original extended-test job, run 36029943322, revision 38c142ec546f5a00949fec568d4ae5b02b428cc4. The captured failure at 2026-09-24 18:04:46 states:
InvalidParameter: The requested VM size Standard_D2s_v7 is not available in the current region.
Azure's returned list includes Standard_D2s_v6. The preceding image-not-found-locally message is not the fatal error; Azure rejected VM creation.
Workaround commit 319a1ac2 restores Standard_D2s_v6, Standard_D4s_v6, Standard_D8s_v6 and Standard_D16s_v6, retaining the existing option labels. It bumps the Windows bundle from 3.0.3 to 3.0.4 so the corrected bundle can be published and registered.
Rerun extended-test job, run 36050551431, revision 319a1ac2d19f1d26c3861c96a1a43a00ceb31dfa. test_create_guacamole_service_into_base_workspace, which creates the Windows VM, passed at 2026-09-24 20:48:08 UTC.
The rerun was not fully green: it ended with 1 failed, 2 passed, 54 deselected, 3 warnings, 1 error in 14153.46s (3:55:53). Later operation polling returned HTTP 401, including at 21:48:25 UTC and during teardown. Those failures are separate from SKU availability. Token expiry is consistent with the timing and the fixed bearer-token headers, but is not proven by HTTP 401 alone. Existing closed issue #3198 describes expired E2E fixture tokens.
Run Deploy Azure TRE (branch) with e2eTestsCustomSelector=extended, environment=CICD and e2eProcesses=1.
Observe Windows VM creation fail in test_create_guacamole_service_into_base_workspace with the unsupported Standard_D2s_v7 size.
Proposed fix
Promote the tested Windows bundle workaround in a separate PR targeting main, to merge after #5048. Restore the four v6 mappings and publish bundle version 3.0.4. This fixes the observed Windows VM deployment failure; it does not add a per-run SKU selector or address the separate authentication failures.
Azure TRE version and affected component
PR #5048 at 38c142ec546f5a00949fec568d4ae5b02b428cc4; tre-service-guacamole-windowsvm version 3.0.3, Windows 11, switzerlandnorth.
Describe the bug
The Guacamole Windows VM bundle in #5048 maps the default
2 CPU | 8GB RAMoption toStandard_D2s_v7. Azure rejected that size in theswitzerlandnorthCI environment, causing the extended Guacamole test to fail when creating its Windows VM.The bundle already exists at
templates/workspace_services/guacamole/user_resources/guacamole-azure-windowsvm/porter.yaml. Commit 2264adeb in #5048 changes its four size mappings from v6 to v7. At the time of filing, #5048 is still open andmainuses v6. This report tracks a separate follow-up fix intended to merge after #5048.Evidence
Original extended-test job, run
36029943322, revision38c142ec546f5a00949fec568d4ae5b02b428cc4. The captured failure at2026-09-24 18:04:46states:Azure's returned list includes
Standard_D2s_v6. The preceding image-not-found-locally message is not the fatal error; Azure rejected VM creation.Workaround commit 319a1ac2 restores
Standard_D2s_v6,Standard_D4s_v6,Standard_D8s_v6andStandard_D16s_v6, retaining the existing option labels. It bumps the Windows bundle from3.0.3to3.0.4so the corrected bundle can be published and registered.Rerun extended-test job, run
36050551431, revision319a1ac2d19f1d26c3861c96a1a43a00ceb31dfa.test_create_guacamole_service_into_base_workspace, which creates the Windows VM, passed at2026-09-24 20:48:08 UTC.The rerun was not fully green: it ended with
1 failed, 2 passed, 54 deselected, 3 warnings, 1 error in 14153.46s (3:55:53). Later operation polling returned HTTP 401, including at21:48:25 UTCand during teardown. Those failures are separate from SKU availability. Token expiry is consistent with the timing and the fixed bearer-token headers, but is not proven by HTTP 401 alone. Existing closed issue #3198 describes expired E2E fixture tokens.Steps to reproduce
38c142ec546f5a00949fec568d4ae5b02b428cc4from Redesign airlock storage account architecture #5048 into theswitzerlandnorthCI environment.Deploy Azure TRE (branch)withe2eTestsCustomSelector=extended,environment=CICDande2eProcesses=1.test_create_guacamole_service_into_base_workspacewith the unsupportedStandard_D2s_v7size.Proposed fix
Promote the tested Windows bundle workaround in a separate PR targeting
main, to merge after #5048. Restore the four v6 mappings and publish bundle version3.0.4. This fixes the observed Windows VM deployment failure; it does not add a per-run SKU selector or address the separate authentication failures.Azure TRE version and affected component
PR #5048 at
38c142ec546f5a00949fec568d4ae5b02b428cc4;tre-service-guacamole-windowsvmversion3.0.3, Windows 11,switzerlandnorth.