As an administrator, I would like to have a more secure way of SSH or RDP to my AWC or DC for management tasks and needing to open port 22 or 3389 to a single IP might cause me to be lazy and just open it to 0.0.0.0/0, which is a really bad security practice, so I would like for Azure Bastion to be deployed by default so I'm encouraged to use amore secure way to SSH/RDP to my VMs.

Problem

Executing terraform apply may intermittently fail with the following error

Error: creating Subnet: (Name "dc-subnet" / Virtual Network Name "vnet-centralus" / Resource Group "cas-mgr-single-connector-r6ikn"): network.SubnetsClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=<nil> Code="AnotherOperationInProgress" Message="Another operation on this or dependent resource is in progress. To retrieve status of the operation use uri: https://management.azure.com/subscriptions/6130794d-3700-4597-8e5d-2b09a0a303c0/providers/Microsoft.Network/locations/centralus/operations/00bf947d-99f9-4df9-963c-b8b28c0d61d2?api-version=2021-05-01." Details=[]

Deployments Affected

• cas-mgr-single-connector
• casm-aadds-single-connector

Cause

Appears to be a dependency/concurrency issue whereby multiple VNet modification operations are attempted simultaneously. Effort is ongoing to identify a minimal reproduction case & potentially introduce explicit dependencies as appropriate.

Workaround

As the issue is intermittent, simply running terraform destroy and re-running terraform apply should be sufficient.

The Ubuntu based Cloud Access Connector is now deprecated and will soon be no longer supported. Please update the Terraform to deploy the RHEL/Rocky Linux based Anyware Connector instead.

Problem

terraform apply may sometimes fail with the message:

Error: waiting for creation of Linux Virtual Machine: (Name "pryqf-scent-0" / Resource Group "cas-mgr-load-balancer-one-ip-nat-pryqf"): Code="RetryableError" Message="A retryable error occurred."
  
    with module.centos-std-vm.azurerm_linux_virtual_machine.centos-std-vm["linux_std_0"],
    on ../../modules/centos-std-vm/main.tf line 50, in resource "azurerm_linux_virtual_machine" "centos-std-vm":
    50: resource "azurerm_linux_virtual_machine" "centos-std-vm" {

Deployments Affected

Potentially all, observed on:

• cas-mgr-load-balancer-one-ip

Cause

Root cause as yet unknown, appears related to this issue on the azurerm terraform provider.

Workaround

As the issue is intermittent, simply running terraform destroy and re-running terraform apply should be sufficient.