Edit

Share via

Known issues in Azure Stack Hub ruggedized

  • Article

This article lists known issues in Azure Stack Hub ruggedized. The list is updated as new issues are identified.

Update

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

  • Applicable: This issue applies to all supported releases.
  • Cause: During update, a process takes a lock on the new content that needs to be copied to CA VM. When the update fails, the lock is released.
  • Remediation: Resume the update.
  • Occurrence: Rare

Portal

Administrative subscriptions

  • Applicable: This issue applies to all supported releases.
  • Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
  • Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
  • Occurrence: Common

Networking

Network Security Groups

DenyAllOutbound rule cannot be created

  • Applicable: This issue applies to all supported releases.

  • Cause: An explicit DenyAllOutbound rule to the internet cannot be created in an NSG during VM creation as this will prevent the communication required for the VM deployment to complete. It will also deny the two essential IPs that are required in order to deploy VMs: DHCP IP:169.254.169.254 and DNS IP: 168.63.129.16.

  • Remediation: Allow outbound traffic to the internet during VM creation, and modify the NSG to block the required traffic after VM creation is complete.

  • Occurrence: Common

Virtual Network Gateway

Documentation

Load Balancer

Load Balancer directing traffic to one backend VM in specific scenarios

  • Applicable: This issue applies to all supported releases.
  • Cause: When enabling Session Affinity on a load balancer, the 2 tuple hash utilizes the PA IP (Physical Address IP) instead of the private IPs assigned to the VMs. In scenarios where traffic directed to the load balancer arrives through a VPN, or if all the client VMs (source IPs) reside on the same node and Session Affinity is enabled, all traffic is directed to one backend VM.
  • Occurrence: Common