Azure Stack Hub 已知问题Azure Stack Hub known issues

本文列出了 Azure Stack Hub 发行版中的已知问题。This article lists known issues in releases of Azure Stack Hub. 每当发现新的问题,此列表就会更新。The list is updated as new issues are identified.

若要访问不同版本的已知问题,请使用左侧目录上方的版本选择器下拉列表。To access known issues for a different version, use the version selector dropdown above the table of contents on the left.

重要

在应用更新之前,请先查看本部分。Review this section before applying the update.

重要

如果 Azure Stack Hub 实例落后于两个以上的更新,则认为它不符合。If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. 必须至少更新到最低支持版本才能获得支持You must update to at least the minimum supported version to receive support.

更新Update

有关已知的 Azure Stack Hub 更新问题,请参阅排查 Azure Stack Hub 中的更新问题For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

门户Portal

管理订阅Administrative subscriptions

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:不应使用版本 1804 中引入的两个管理订阅。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

如果 NIC 未附加到运行中的 VM,则无法删除 NSGCannot delete an NSG if NICs not attached to running VM

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:如果取消关联 NSG 和未附加到运行中 VM 的 NIC,则该对象的更新 (PUT) 操作会在网络控制器层失败。Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. NSG 将在网络资源提供程序层(而不是网络控制器上)更新,因此 NSG 转变为失败状态。The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
  • 补救措施:将与 NSG 相关联的 NIC 附加到运行中的 VM,然后取消与 NSG 的关联,或者删除与 NSG 关联的所有 NIC。Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
  • 发生次数:通用Occurrence: Common

无法创建 DenyAllOutbound 规则DenyAllOutbound rule cannot be created

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:VM 创建期间无法在 NSG 中创建到 Internet 的显式 DenyAllOutbound 规则,因为这会使 VM 部署所需的通信无法完成。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.
  • 补救措施:VM 创建期间允许出站流量流向 Internet,并在 VM 创建完成后修改 NSG 以阻止所需的流量。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

在特定情况下将流量定向到一个后端 VM 的负载均衡器Load Balancer directing traffic to one backend VM in specific scenarios

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在负载均衡器上启用“会话相关性”时,2 元组哈希使用 PA IP(物理地址 IP)而不是分配给 VM 的专用 IP。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. 如果定向到负载均衡器的流量通过 VPN 到达,或者,如果所有客户端 VM(源 IP)位于同一节点上并且启用了会话相关性,则所有流量都将定向到一个后端 VM。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

公共 IPPublic IP

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法更改与负载均衡器关联的公共 IP 的 IdleTimeoutInMinutes 值。Cause: The IdleTimeoutInMinutes value for a public IP that is associated to a load balancer cannot be changed. 该操作会将公共 IP 置于失败状态。The operation puts the public IP into a failed state.
  • 补救措施:若要使公共 IP 恢复成功状态,请将引用公共 IP 的负载均衡器规则上的 IdleTimeoutInMinutes 值更改回原始值(默认值为 4 分钟)。Remediation: To bring the public IP back into a successful state, change the IdleTimeoutInMinutes value on the load balancer rule that references the public IP back to the original value (the default is 4 minutes).
  • 发生次数:通用Occurrence: Common

计算Compute

使用门户部署 Standard_DS2_v2 大小的虚拟机规模集时遇到的问题Issues deploying virtual machine scale set with Standard_DS2_v2 size using the portal

  • 适用于:此问题适用于 2005 版本。Applicable: This issue applies to the 2005 release.
  • 原因:门户 bug 导致创建 Standard_DS2_v2 大小的规模集失败。Cause: A portal bug causes scale set creation with Standard_DS2_v2 size to fail.
  • 补救措施:使用 PowerShell 或 CLI 部署此虚拟机规模集 VM 大小。Remediation: Use PowerShell or CLI to deploy this virtual machine scale set VM size.

在 Ubuntu Server 20.04 中使用 VM 扩展时遇到的问题Issues using VM extensions in Ubuntu Server 20.04

  • 适用于:此问题适用于 Ubuntu Server 20.04 LTS。Applicable: This issue applies to Ubuntu Server 20.04 LTS.
  • 原因:某些 Linux 发行版已转换为 Python 3.8,并完全删除了 Python 的旧版 /usr/bin/python 入口点。Cause: Some Linux distributions have transitioned to Python 3.8 and removed the legacy /usr/bin/python entrypoint for Python altogether. 已转换到 Python 3.x 的 Linux 发行版用户在尝试将这些扩展部署到自己的 VM 之前,必须确保存在旧版 /usr/bin/python 入口点。Linux distribution users who have transitioned to Python 3.x must ensure the legacy /usr/bin/python entry point exists before attempting to deploy those extensions to their VMs. 否则,扩展部署可能会失败。Otherwise, the extension deployment might fail.
  • 补救措施:请按照在启用 Python 3 的 Linux Azure 虚拟机系统中使用 VM 扩展时遇到的问题中的解决步骤操作,但请跳过步骤 2,因为 Azure Stack Hub 没有“运行命令”功能。Remediation: Follow the resolution steps in Issues using VM extensions in Python 3-enabled Linux Azure Virtual Machines systems but skip step 2, because Azure Stack Hub does not have the Run command functionality.

门户上的 NVv4 VM 大小NVv4 VM size on portal

  • 适用于:此问题适用于 2002 及更高版本。Applicable: This issue applies to 2002 and later.
  • 原因:完成 VM 创建体验后,你将看到 VM 大小:NV4as_v4。Cause: When going through the VM creation experience, you will see the VM size: NV4as_v4. 如果客户拥有基于 AMD MI25 的 Azure Stack Hub GPU 预览版所需的硬件,那么这些客户可以成功部署 VM。Customers who have the hardware required for the AMD MI25-based Azure Stack Hub GPU preview are able to have a successful VM deployment. 所有其他客户将无法使用此 VM 大小部署 VM。All other customers will have a failed VM deployment with this VM size.
  • 补救措施:按照设计为 Azure Stack Hub GPU 预览版做准备。Remediation: By design in preparation for the Azure Stack Hub GPU preview.

已消耗的计算配额Consumed compute quota

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建新虚拟机时,可能会收到一则错误消息,例如“此订阅在此位置的区域 vCPU 总数已达到上限。此订阅使用了所有可用的 50 个区域 vCPU”。Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. 这表示可用的核心配额总计已达到上限。This indicates that the quota for total cores available to you has been reached.
  • 补救措施:请求操作员提供配额更高的附加计划。Remediation: Ask your operator for an add-on plan with additional quota. 编辑当前计划的配额不起作用,也不会反映提高的配额。Editing the current plan's quota will not work or reflect increased quota.
  • 发生次数:罕见Occurrence: Rare

VM 概述边栏选项卡未显示正确的计算机名称VM overview blade does not show correct computer name

  • 适用于:此问题适用于所有版本。Applicable: This issue applies to all releases.
  • 原因:在概述边栏选项卡中查看 VM 的详细信息时,计算机名称显示为“(不可用)”。Cause: When viewing details of a VM in the overview blade, the computer name shows as (not available). 这是针对从专用磁盘/磁盘快照创建的 VM 设计的,也会为市场映像而出现。This is by design for VMs created from specialized disks/disk snapshots, and appears for Marketplace images as well.
  • 补救措施:在“设置”下查看“属性”边栏选项卡。Remediation: View the Properties blade under Settings.

虚拟机规模集Virtual machine scale set

在 4 节点的 Azure Stack Hub 环境中进行修补和更新时出现故障Create failures during patch and update on 4-node Azure Stack Hub environments

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在包含 3 个容错域的可用性集中创建 VM 以及创建虚拟机规模集实例失败,在一个 4 节点 Azure Stack Hub 环境中进行更新时出现 FabricVmPlacementErrorUnsupportedFaultDomainSize 错误。Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
  • 补救措施:可以在包含 2 个容错域的可用性集中成功创建单一 VM。Remediation: You can create single VMs in an availability set with 2 fault domains successfully. 但是,在 4 节点 Azure Stack Hub 部署中进行更新时,仍然不能创建规模集实例。However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

存储Storage

保留期恢复为 0Retention period reverts to 0

  • 适用于:此问题适用于版本 2002 和 2005。Applicable: This issue applies to releases 2002 and 2005.
  • 原因:如果在保留期设置中指定非 0 的时间段,则它将在 2002 或 2005 更新期间恢复为 0(此设置的默认值)。Cause: If you specify a time period other than 0 in the retention period setting, it reverts to 0 (the default value of this setting) during the 2002 or 2005 update. 这个 0 天的设置将在更新完成后立即生效,从而导致所有现有已删除的存储帐户和任何即将新删除的存储帐户立即不予保留,并标记为需要进行定期垃圾回收(每小时运行一次)。The 0 days setting takes effect immediately after the update finishes, which causes all existing deleted storage accounts and any upcoming newly deleted storage accounts to be immediately out of retention and marked for periodic garbage collection (which runs hourly).
  • 补救措施:将保留期手动指定为正确的时间段。Remediation: Manually specify the retention period to a correct period. 在指定新的保留期之前已进行垃圾回收的任何存储帐户都不可恢复。Any storage account that has already been garbage collected before the new retention period is specified, is not recoverable.

资源提供程序Resource providers

SQL/MySQLSQL/MySQL

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to release 2002.
  • 原因:如果标记包含 SQL 资源提供程序 (RP) 版本 1.1.33.0 或更早版本,则在更新标记时,不会加载 SQL/MySQL 的边栏选项卡。Cause: If the stamp contains SQL resource provider (RP) version 1.1.33.0 or earlier, upon update of the stamp, the blades for SQL/MySQL do not load.
  • 补救措施:将 RP 更新到版本 1.1.47.0。Remediation: Update the RP to version 1.1.47.0.

应用服务App Service

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to release 2002.
  • 原因:如果标记包含应用服务资源提供程序 (RP) 版本 1.7 和更早版本,则在更新标记时,不会加载应用服务的边栏选项卡。Cause: If the stamp contains App Service resource provider (RP) version 1.7 and older, upon update of the stamp, the blades for App Service do not load.
  • 补救措施:将 RP 更新到版本 2002 Q2。Remediation: Update the RP to version 2002 Q2.

更新Update

应用 2002 更新后,管理员门户中可能会错误地显示“时间源无效”警报。After applying the 2002 update, an alert for an "Invalid Time Source" may incorrectly appear in the Administrator portal. 这个警报是可忽略的误报,会在即将发布的版本中得到解决。This false-positive alert can be ignored and will be fixed in an upcoming release.

有关已知的 Azure Stack Hub 更新问题,请参阅排查 Azure Stack Hub 中的更新问题For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

门户Portal

管理订阅Administrative subscriptions

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:不应使用版本 1804 中引入的两个管理订阅。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

订阅权限Subscription permissions

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法使用 Azure Stack Hub 门户查看订阅的权限。Cause: You cannot view permissions to your subscription using the Azure Stack Hub portals.
  • 补救措施:使用 PowerShell 验证权限Remediation: Use PowerShell to verify permissions.
  • 发生次数:通用Occurrence: Common

存储帐户选项Storage account options

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,存储帐户名称显示为“存储帐户 - Blob、文件、表、队列”;但是,Azure Stack Hub 不支持“文件”。 Cause: In the user portal, the name of storage accounts is shown as Storage account - blob, file, table, queue ; however, file is not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

创建托管磁盘快照Create Managed Disk snapshot

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to release 2002.
  • 原因:在用户门户中创建托管磁盘快照时,“帐户类型”框为空。Cause: In the user portal, when creating a Managed Disk snapshot, the Account type box is empty. 选择“创建”按钮时,如果帐户类型为空,则快照创建将失败。When you select the Create button with an empty account type, the snapshot creation fails.
  • 补救措施:从“帐户类型”下拉列表中选择一种帐户类型,然后创建快照。Remediation: Select an account type from the Account type dropdown list, then create the snapshot.
  • 发生次数:通用Occurrence: Common

网络接口已断开连接的警报Alert for network interface disconnected

  • 适用于:此问题适用于 1908 及更高版本。Applicable: This issue applies to 1908 and later.
  • 原因:当线缆与网络适配器断开连接时,管理员门户中不显示警报。Cause: When a cable is disconnected from a network adapter, an alert does not show in the administrator portal. 此问题的原因是 Windows Server 2019 中默认会禁用此故障。This issue is caused because this fault is disabled by default in Windows Server 2019.
  • 发生次数:通用Occurrence: Common

网络Networking

无法创建 DenyAllOutbound 规则DenyAllOutbound rule cannot be created

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:VM 创建期间无法在 NSG 中创建到 Internet 的显式 DenyAllOutbound 规则,因为这会使 VM 部署所需的通信无法完成。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.
  • 补救措施:VM 创建期间允许出站流量流向 Internet,并在 VM 创建完成后修改 NSG 以阻止所需的流量。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

NSG 规则不支持 ICMP 协议ICMP protocol not supported for NSG rules

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建入站或出站网络安全规则时,“协议”选项显示“ICMP”选项。Cause: When creating an inbound or an outbound network security rule, the Protocol option shows an ICMP option. Azure Stack Hub 目前不支持此选项。This is currently not supported on Azure Stack Hub. 此问题已修复,不会出现在下一个 Azure Stack Hub 版本中。This issue is fixed and will not appear in the next Azure Stack Hub release.
  • 发生次数:通用Occurrence: Common

如果 NIC 未附加到运行中的 VM,则无法删除 NSGCannot delete an NSG if NICs not attached to running VM

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:如果取消关联 NSG 和未附加到运行中 VM 的 NIC,则该对象的更新 (PUT) 操作会在网络控制器层失败。Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. NSG 将在网络资源提供程序层(而不是网络控制器上)更新,因此 NSG 转变为失败状态。The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
  • 补救措施:将与 NSG 相关联的 NIC 附加到运行中的 VM,然后取消与 NSG 的关联,或者删除与 NSG 关联的所有 NIC。Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
  • 发生次数:通用Occurrence: Common

在特定情况下将流量定向到一个后端 VM 的负载均衡器Load Balancer directing traffic to one backend VM in specific scenarios

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在负载均衡器上启用“会话相关性”时,2 元组哈希使用 PA IP(物理地址 IP)而不是分配给 VM 的专用 IP。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. 如果定向到负载均衡器的流量通过 VPN 到达,或者,如果所有客户端 VM(源 IP)位于同一节点上并且启用了会话相关性,则所有流量都将定向到一个后端 VM。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

LinuxNetwork interface

添加/删除网络接口Adding/removing network interface

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:新网络接口无法添加到处于“正在运行”状态的 VM。Cause: A new network interface cannot be added to a VM that is in a running state.
  • 补救措施:添加或删除网络接口之前,先停止虚拟机。Remediation: Stop the virtual machine before adding or removing a network interface.
  • 发生次数:通用Occurrence: Common

主网络接口Primary network interface

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法更改 VM 的主要 NIC。Cause: The primary NIC of a VM cannot be changed. 删除或分离主要 NIC 导致启动 VM 时出现问题。Deleting or detaching the primary NIC results in issues when starting up the VM.
  • 发生次数:通用Occurrence: Common

公共 IPPublic IP

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法更改与负载均衡器关联的公共 IP 的 IdleTimeoutInMinutes 值。Cause: The IdleTimeoutInMinutes value for a public IP that is associated to a load balancer cannot be changed. 该操作会将公共 IP 置于失败状态。The operation puts the public IP into a failed state.
  • 补救措施:若要使公共 IP 恢复成功状态,请将引用公共 IP 的负载均衡器规则上的 IdleTimeoutInMinutes 值更改回原始值(默认值为 4 分钟)。Remediation: To bring the public IP back into a successful state, change the IdleTimeoutInMinutes value on the load balancer rule that references the public IP back to the original value (the default value is 4 minutes).
  • 发生次数:通用Occurrence: Common

虚拟网络网关Virtual Network Gateway

文档Documentation

计算Compute

无法在门户中使用 Standard_DS2_v2 VM 大小创建规模集Cannot create a virtual machine scale set with Standard_DS2_v2 VM size on portal

  • 适用于:此问题适用于 2002 版本。Applicable: This issue applies to the 2002 release.
  • 原因:存在一个门户 bug,它阻止使用Standard_DS2_v2 VM 大小创建规模集。Cause: There is a portal bug that prevents virtual machine scale set creation with the Standard_DS2_v2 VM size. 创建即会产生错误:“{"code":"DeploymentFailed","message":":"至少一项资源部署操作失败。Creating one will error out with: "{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. 请列出部署操作以获取详细信息。Please list deployment operations for details. 请参阅 https://aka.ms/arm-debug 了解使用情况详细信息。","details":[{"code":"BadRequest","message":"{\r\n " error": {\r\n " code":" NetworkProfileValidationError" ,\r\n " message":" 虚拟机大小 Standard_DS2_v2 不在 VM 大小的允许列表中,不能在 VM 规模集 /subscriptions/x/resourceGroups/RGVMSS/providers/Microsoft.Compute/virtualMachineScaleSets/vmss 的索引 0 处的 VM 上启用加速网络。Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n "error": {\r\n "code": "NetworkProfileValidationError",\r\n "message": "Virtual Machine size Standard_DS2_v2 is not in the allowed list of VM sizes for accelerated networking to be enabled on the VM at index 0 for VM Scale Set /subscriptions/x/resourceGroups/RGVMSS/providers/Microsoft.Compute/virtualMachineScaleSets/vmss. 允许的大小:."\r\n }\r\n}"}]}"Allowed sizes: ."\r\n }\r\n}"}]}"
  • 补救措施:使用 PowerShell 或资源管理器模板创建虚拟机规模集。Remediation: Create a virtual machine scale set with PowerShell or a resource manager template.

VM 概述边栏选项卡未显示正确的计算机名称VM overview blade does not show correct computer name

  • 适用于:此问题适用于所有版本。Applicable: This issue applies to all releases.
  • 原因:在概述边栏选项卡中查看 VM 的详细信息时,计算机名称显示为“(不可用)”。Cause: When viewing details of a VM in the overview blade, the computer name shows as (not available). 这是针对从专用磁盘/磁盘快照创建的 VM 设计的,也会为市场映像而出现。This is by design for VMs created from specialized disks/disk snapshots, and appears for Marketplace images as well.
  • 补救措施:在“设置”下查看“属性”边栏选项卡。Remediation: View the Properties blade under Settings.

门户上的 NVv4 VM 大小NVv4 VM size on portal

  • 适用于:此问题适用于版本 2002 及更高版本。Applicable: This issue applies to release 2002 and later.
  • 原因:完成 VM 创建体验后,你将看到 VM 大小:NV4as_v4。Cause: When going through the VM creation experience, you will see the VM size: NV4as_v4. 如果客户拥有基于 AMD MI25 的 Azure Stack Hub GPU 预览版所需的硬件,那么这些客户可以成功部署 VM。Customers who have the hardware required for the AMD MI25-based Azure Stack Hub GPU preview are able to have a successful VM deployment. 所有其他客户将无法使用此 VM 大小部署 VM。All other customers will have a failed VM deployment with this VM size.
  • 补救措施:按照设计为 Azure Stack Hub GPU 预览版做准备。Remediation: By design in preparation for the Azure Stack Hub GPU preview.

VM 启动诊断VM boot diagnostics

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建新的虚拟机 (VM) 时,可能会显示以下错误: 无法启动虚拟机 'vm-name'。错误:无法更新 VM 'vm-name' 的串行输出设置Cause: When creating a new virtual machine (VM), the following error might be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. 如果在 VM 上启用了启动诊断,但删除了启动诊断存储帐户,则会发生该错误。The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
  • 补救措施:使用以前所用的相同名称重新创建存储帐户。Remediation: Recreate the storage account with the same name you used previously.
  • 发生次数:通用Occurrence: Common

VM 启动诊断VM boot diagnostics

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:尝试启动“已停止-解除分配”的虚拟机时,可能会显示以下错误:“找不到 VM 诊断存储帐户 "diagnosticstorageaccount"。请确保未删除存储帐户”。Cause: When trying to start a stop-deallocated virtual machine,the following error might be displayed: VM diagnostics Storage account 'diagnosticstorageaccount' not found. Ensure storage account is not deleted. 如果尝试在启用了启动诊断的情况下启动 VM,但引用的启动诊断存储帐户被删除,则会发生此错误。The error occurs if you attempt to start a VM with boot diagnostics enabled, but the referenced boot diagnostics storage account is deleted.
  • 补救措施:使用以前所用的相同名称重新创建存储帐户。Remediation: Recreate the storage account with the same name you used previously.
  • 发生次数:通用Occurrence: Common

已消耗的计算配额Consumed compute quota

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建新虚拟机时,可能会收到一则错误消息,例如“此订阅在此位置的区域 vCPU 总数已达到上限。此订阅使用了所有可用的 50 个区域 vCPU”。Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. 这表示可用的核心配额总计已达到上限。This indicates that the quota for total cores available to you has been reached.
  • 补救措施:请求操作员提供配额更高的附加计划。Remediation: Ask your operator for an add-on plan with additional quota. 编辑当前计划的配额不起作用,也不会反映提高的配额。Editing the current plan's quota will not work or reflect increased quota.
  • 发生次数:罕见Occurrence: Rare

虚拟机规模集Virtual machine scale set

在 4 节点的 Azure Stack Hub 环境中进行修补和更新时出现故障Create failures during patch and update on 4-node Azure Stack Hub environments

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在包含 3 个容错域的可用性集中创建 VM 以及创建虚拟机规模集实例失败,在一个 4 节点 Azure Stack Hub 环境中进行更新时出现 FabricVmPlacementErrorUnsupportedFaultDomainSize 错误。Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
  • 补救措施:可以在包含 2 个容错域的可用性集中成功创建单一 VM。Remediation: You can create single VMs in an availability set with 2 fault domains successfully. 但是,在 4 节点 Azure Stack Hub 部署中进行更新时,仍然不能创建规模集实例。However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

SQL VMSQL VM

配置自动备份时存储帐户创建失败Storage account creating failure when configuring Auto Backup

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to 2002.
  • 原因:当使用新的存储帐户配置 SQL VM 的自动备份时,它会失败并显示错误“部署模板验证失败。找不到 "SqlAutobackupStorageAccountKind" 的模板参数。”Cause: When configuring the automated backup of SQL VMs with a new storage account, it fails with the error Deployment template validation failed. The template parameter for 'SqlAutobackupStorageAccountKind' is not found.
  • 补救措施:应用最新的 2002 修补程序。Remediation: Apply the latest 2002 hotfix.

无法在启用了 TLS 1.2 的情况下配置自动备份Auto backup cannot be configured with TLS 1.2 enabled

  • 适用于:此问题适用于新安装的 2002 及更高版本,或任何启用了 TLS 1.2 的早期版本。Applicable: This issue applies to new installations of 2002 and later, or any previous release with TLS 1.2 enabled.
  • 原因:当使用现有存储帐户配置 SQL VM 的自动备份时,它会失败并显示错误“SQL Server IaaS 代理:基础连接已关闭:发送时出现意外错误。”Cause: When configuring the automated backup of SQL VMs with an existing storage account, it fails with the error SQL Server IaaS Agent: The underlying connection was closed: An unexpected error occurred on a send.
  • 发生次数:通用Occurrence: Common

存储Storage

保留期恢复为 0Retention period revert to 0

  • 适用于:此问题适用于版本 2002 和 2005。Applicable: This issue applies to release 2002 and 2005.
  • 原因:如果以前在保留期设置中指定了非 0 的时间段,则它将在 2002 或 2005 更新期间恢复回 0(此设置的默认值)。Cause: If you previously specified a time period other than 0 in retention period setting, it would be reverted back to 0 (the default value of this setting) during 2002 and 2005 update. 这个 0 天的设置会在更新完成后立即生效,从而导致所有现有已删除的存储帐户和任何即将新删除的存储帐户立即不予保留,并标记为需要进行定期垃圾回收(每小时运行一次)。And the 0 days setting would take effect immdiately after update finished, which causes all the existing deleted storage accounts and any upcoming newly deleted storage account being immediately out of retention and marked for periodic garbage collection (which runs hourly).
  • 补救措施:将保留期手动指定为正确的时间段。Remediation: Manually specify the retention period to a proper period. 但是,在指定新的保留期之前已进行垃圾回收的任何存储帐户都不可恢复。However, any storage account already been garbage collected before the new retention period is specified is not recoverable.

资源提供程序Resource providers

SQL/MySQLSQL/MySQL

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to release 2002.
  • 原因:如果标记包含 SQL 资源提供程序 (RP) 版本 1.1.33.0 或更早版本,则在更新标记时,不会加载 SQL/MySQL 的边栏选项卡。Cause: If the stamp contains SQL resource provider (RP) version 1.1.33.0 or earlier, upon update of the stamp, the blades for SQL/MySQL will not load.
  • 补救措施:将 RP 更新到版本 1.1.47.0Remediation: Update the RP to version 1.1.47.0

应用服务App Service

  • 适用于:此问题适用于版本 2002。Applicable: This issue applies to release 2002.
  • 原因:如果标记包含应用服务资源提供程序 (RP) 版本 1.7 和更早版本,则在更新标记时,不会加载应用服务的边栏选项卡。Cause: If the stamp contains App Service resource provider (RP) version 1.7 and older, upon update of the stamp, the blades for App Service do not load.
  • 补救措施:将 RP 更新到版本 2020 Q2Remediation: Update the RP to version 2020 Q2.

更新Update

有关已知的 Azure Stack Hub 更新问题,请参阅排查 Azure Stack Hub 中的更新问题For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

门户Portal

管理订阅Administrative subscriptions

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:不应使用版本 1804 中引入的两个管理订阅。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

“锁定”边栏选项卡中的重复“订阅”按钮Duplicate Subscription button in Lock blade

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在管理员门户中,用户订阅的“锁定”边栏选项卡有两个按钮,显示“订阅”。Cause: In the administrator portal, the Lock blade for user subscriptions has two buttons that say Subscription.
  • 发生次数:通用Occurrence: Common

订阅权限Subscription permissions

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法使用 Azure Stack Hub 门户查看订阅的权限。Cause: You cannot view permissions to your subscription using the Azure Stack Hub portals.
  • 补救措施:使用 PowerShell 验证权限Remediation: Use PowerShell to verify permissions.
  • 发生次数:通用Occurrence: Common

存储帐户设置Storage account settings

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,存储帐户的“配置”边栏选项卡显示用于更改 安全传输类型 的选项。Cause: In the user portal, the storage account Configuration blade shows an option to change security transfer type. Azure Stack Hub 目前不支持此功能。The feature is currently not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

使用 OAuth 上传 Blob 时出错Upload blob with OAuth error

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中尝试使用“OAuth(preview)”选项上传 Blob 时,任务将会失败并出现错误消息。Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
  • 补救措施:使用 SAS 选项上传 Blob。Remediation: Upload the blob using the SAS option.
  • 发生次数:通用Occurrence: Common

不支持上传 Blob 选项Upload blob option unsupported

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中尝试从“上传”边栏选项卡上传 Blob 时,有一个选项可用于选择“AAD”或“密钥身份验证”,但是,Azure Stack Hub 不支持“AAD”。 Cause: In the user portal, when you try to upload a blob in the upload blade, there is an option to select AAD or Key Authentication , however AAD is not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

网络接口已断开连接的警报Alert for network interface disconnected

  • 适用于:此问题适用于 1908 及更高版本。Applicable: This issue applies to 1908 and above.
  • 原因:当线缆与网络适配器断开连接时,管理员门户中不显示警报。Cause: When a cable is disconnected from a network adapter, an alert does not show in the administrator portal. 此问题的原因是 Windows Server 2019 中默认会禁用此故障。This issue is caused because this fault is disabled by default in Windows Server 2019.
  • 发生次数:通用Occurrence: Common

创建 VM 时出现不正确的工具提示Incorrect tooltip when creating VM

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中选择类型为“高级 SSD”的托管磁盘时,下拉列表显示“OS 磁盘”。Cause: In the user portal, when you select a managed disk, with disk type Premium SSD, the drop-down list shows OS Disk. 该选项旁边的工具提示显示“可以通过 Azure 试用帐户免费使用某些 OS 磁盘大小”;但是,这对于 Azure Stack Hub 而言是不正确的。The tooltip next to that option says Certain OS Disk sizes may be available for free with Azure trial Account ; however, this is not valid for Azure Stack Hub. 此外,该列表包含“符合免费帐户的条件”,而这对 Azure Stack Hub 而言也是不正确的。In addition, the list includes Free account eligible which is also not valid for Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

删除存储容器Delete a storage container

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,当用户尝试删除存储容器时,如果用户未切换到“替代 Azure Policy 和 RBAC 角色设置”,则该操作将会失败。Cause: In the user portal, when a user attempts to delete a storage container, the operation fails when the user does not toggle Override Azure Policy and RBAC Role settings.
  • 补救措施:确保已选中“替代 Azure Policy 和 RBAC 角色设置”框。Remediation: Ensure that the box is checked for Override Azure Policy and RBAC Role settings.
  • 发生次数:通用Occurrence: Common

虚拟机上的刷新按钮失效Refresh button on virtual machines fails

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中导航到“虚拟机”并尝试使用顶部的按钮进行刷新时,状态无法准确更新。Cause: In the user portal, when you navigate to Virtual Machines and try to refresh using the button at the top, the states fail to update accurately.
  • 补救措施:无论是否已按下刷新按钮,状态每隔 5 分钟都会自动更新。Remediation: The status is automatically updated every 5 minutes regardless of whether the refresh button has been clicked or not. 请等待 5 分钟,然后检查状态。Wait 5 minutes and check the status.
  • 发生次数:通用Occurrence: Common

存储帐户选项Storage account options

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,存储帐户名称显示为“存储帐户 - Blob、文件、表、队列”;但是,Azure Stack Hub 不支持“文件”。 Cause: In the user portal, the name of storage accounts is shown as Storage account - blob, file, table, queue ; however, file is not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

存储帐户配置Storage account configuration

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中创建存储帐户并查看其“配置”时,无法保存配置更改,因为这会导致 AJAX 错误。Cause: In the user portal, when you create a storage account and view its Configuration , you cannot save configuration changes, as it results in an AJAX error.
  • 发生次数:通用Occurrence: Common

SQL 资源提供程序中的容量监视保持正在加载状态Capacity monitoring in SQL resource provider keeps loading

  • 适用于:此问题适用于已安装 SQL 资源提供程序 1.1.33.0 或更低版本的 Azure Stack Hub 1910 更新或更高版本。Applicable: This issue applies to the Azure Stack Hub 1910 update or later, with SQL resource provider version 1.1.33.0 or earlier installed.
  • 原因:当前的 SQL 资源提供程序版本与 1910 更新中最新的一些门户更改不兼容。Cause: The current version of the SQL resource provider is not compatible with some of the latest portal changes in the 1910 update.
  • 补救措施:将 Azure Stack Hub 升级到 1910 更新后,请按照资源提供程序更新过程应用 SQL 资源提供程序修补程序 1.1.47.0(SQL RP 版本 1.1.47.0)。Remediation: Follow the resource provider update process to apply the SQL resource provider hotfix 1.1.47.0 after Azure Stack Hub is upgraded to the 1910 update (SQL RP version 1.1.47.0). 对于 MySQL 资源提供程序,我们还建议在将 Azure Stack Hub 升级到 1910 更新后,应用 MySQL 资源提供程序修补程序 1.1.47.0(MySQL RP 版本 1.1.47.0)。For the MySQL resource provider, it is also recommended that you apply the MySQL resource provider hotfix 1.1.47.0 after Azure Stack Hub is upgraded to 1910 update (MySQL RP version 1.1.47.0).
  • 发生次数:通用Occurrence: Common

访问控制 (IAM)Access Control (IAM)

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:IAM 扩展已过时。Cause: The IAM extension is out of date. Azure Stack Hub 随附的 Ibiza 门户引入了新的行为,如果用户针对未在全局订阅选择器(用户门户中的“目录 + 订阅”)中选择的订阅打开“访问控制(IAM)”边栏选项卡,则会导致 RBAC 扩展失败。 The Ibiza portal that shipped with Azure Stack Hub introduces a new behavior that causes the RBAC extension to fail if the user is opening the Access Control (IAM) blade for a subscription that is not selected in the global subscription selector ( Directory + Subscription in the user portal). 该边栏选项卡反复显示“正在加载”,且用户无法将新角色添加到订阅。The blade displays Loading in a loop, and the user cannot add new roles to the subscription. “添加”边栏选项卡也反复显示“正在加载”。 The Add blade also displays Loading in a loop.
  • 补救措施:确保已在“目录 + 订阅”菜单中选中该订阅。Remediation: Ensure that the subscription is checked in the Directory + Subscription menu. 可以从门户顶部、“通知”按钮附近,或通过显示以下内容的“所有资源”边栏选项卡上的快捷方式来访问此菜单:“看不到订阅? 请打开‘目录 + 订阅’设置”。The menu can be accessed from the top of the portal, near the Notifications button, or via the shortcut on the All resources blade that displays Don't see a subscription? Open Directory + Subscription settings. 必须在此菜单中选择该订阅。The subscription must be selected in this menu.

SQL 资源提供程序SQL resource provider

  • 适用于:此问题适用于运行 1908 或更低版本的阵列。Applicable: This issue applies to stamps that are running 1908 or earlier.
  • 原因:部署 SQL 资源提供程序 (RP) 版本 1.1.47.0 时,门户不显示与 SQL RP 关联的任何资产。Cause: When deploying the SQL resource provider (RP) version 1.1.47.0, the portal shows no assets other than those associated with the SQL RP.
  • 补救措施:删除 RP、升级阵列,然后重新部署 SQL RP。Remediation: Delete the RP, upgrade the stamp, and re-deploy the SQL RP.

“活动日志”边栏选项卡Activity log blade

  • 适用于:此问题适用于运行 1907 或更高版本的阵列。Applicable: This issue applies to stamps that are running 1907 or later.
  • 原因:访问活动日志时,门户只显示条目的第一页。Cause: When accessing the activity log, the portal only shows the first page of entries. 加载更多结果 将不会加载附加条目。Load more results will not load addition entries.
  • 补救措施:调整筛选器中的时间范围,以查看第一页之后的条目。Remediation: Adjust the time range in the filter to review entries that fall after the first page.

网络Networking

负载均衡器Load balancer

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:将可用性集 VM 添加到负载均衡器的后端池时,门户上显示错误消息,指出“无法保存负载均衡器后端池”。Cause: When adding availability set VMs to the backend pool of a load balancer, an error message is displayed on the portal stating Failed to save load balancer backend pool. 这是门户的表面问题;此功能仍在起作用,VM 在内部已成功添加到后端池。This is a cosmetic issue on the portal; the functionality is still in place and VMs are successfully added to the backend pool internally.
  • 发生次数:通用Occurrence: Common

网络安全组Network Security Groups

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法在 NSG 中创建显式 DenyAllOutbound 规则,因为这会使 VM 部署所需的基础结构无法完成所有内部通信。Cause: An explicit DenyAllOutbound rule cannot be created in an NSG as this will prevent all internal communication to infrastructure needed for the VM deployment to complete.
  • 发生次数:通用Occurrence: Common

服务终结点Service endpoints

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,“虚拟网络”边栏选项卡显示使用“服务终结点”的选项。 Cause: In the user portal, the Virtual Network blade shows an option to use Service Endpoints. Azure Stack Hub 目前不支持此功能。This feature is currently not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

如果 NIC 未附加到运行中的 VM,则无法删除 NSGCannot delete an NSG if NICs not attached to running VM

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:如果取消关联 NSG 和未附加到运行中 VM 的 NIC,则该对象的更新 (PUT) 操作会在网络控制器层失败。Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. NSG 将在网络资源提供程序层(而不是网络控制器上)更新,因此 NSG 转变为失败状态。The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
  • 补救措施:将与 NSG 相关联的 NIC 附加到运行中的 VM,然后取消与 NSG 的关联,或者删除与 NSG 关联的所有 NIC。Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
  • 发生次数:通用Occurrence: Common

LinuxNetwork interface

添加/删除网络接口Adding/removing network interface

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:新网络接口无法添加到处于“正在运行”状态的 VM。Cause: A new network interface cannot be added to a VM that is in a running state.
  • 补救措施:添加或删除网络接口之前,先停止虚拟机。Remediation: Stop the virtual machine before adding or removing a network interface.
  • 发生次数:通用Occurrence: Common

主网络接口Primary network interface

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:无法更改 VM 的主要 NIC。Cause: The primary NIC of a VM cannot be changed. 删除或分离主要 NIC 导致启动 VM 时出现问题。Deleting or detaching the primary NIC results in issues when starting up the VM.
  • 发生次数:通用Occurrence: Common

虚拟网络网关Virtual Network Gateway

下一跃点类型Next Hop Type

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中创建路由表时,“虚拟网络网关”显示为下一跃点类型选项;但是,Azure Stack Hub 不支持此类型。Cause: In the user portal, when you create a route table, Virtual Network gateway appears as one of the next hop type options; however, this is not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

警报Alerts

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,“虚拟网络网关”边栏选项卡显示使用“警报”的选项。 Cause: In the user portal, the Virtual Network Gateway blade shows an option to use Alerts. Azure Stack Hub 目前不支持此功能。This feature is currently not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

主动-主动Active-Active

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户(创建期间)和“虚拟网络网关”的资源菜单中,看到用于启用“主动-主动”配置的选项。 Cause: In the user portal, while creating, and in the resource menu of Virtual Network Gateway , you will see an option to enable Active-Active configuration. Azure Stack Hub 目前不支持此功能。This feature is currently not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

VPN 故障排除程序VPN troubleshooter

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在用户门户中,“连接”边栏选项卡显示一项名为“VPN 故障排除程序”的功能。 Cause: In the user portal, the Connections blade displays a feature called VPN Troubleshooter. Azure Stack Hub 目前不支持此功能。This feature is currently not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

VPN 故障排除程序VPN troubleshooter

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:用户门户显示 VPN 网关资源中的“VPN 故障排除”功能和“指标”,但这在 Azure Stack Hub 中不受支持。 Cause: In the user portal, the VPN Troubleshoot feature and Metrics in a VPN gateway resource appears, however this is not supported in Azure Stack Hub.
  • 发生次数:通用Occurrence: Common

文档Documentation

计算Compute

VM 启动诊断VM boot diagnostics

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建新的 Windows 虚拟机 (VM) 时,可能会显示以下错误: 无法启动虚拟机 'vm-name'。错误:无法更新 VM 'vm-name' 的串行输出设置Cause: When creating a new Windows virtual machine (VM), the following error might be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. 如果在 VM 上启用了启动诊断,但删除了启动诊断存储帐户,则会发生该错误。The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
  • 补救措施:使用以前所用的相同名称重新创建存储帐户。Remediation: Recreate the storage account with the same name you used previously.
  • 发生次数:通用Occurrence: Common

已消耗的计算配额Consumed compute quota

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:创建新虚拟机时,可能会收到一则错误消息,例如“此订阅在此位置的区域 vCPU 总数已达到上限。此订阅使用了所有可用的 50 个区域 vCPU”。Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. 这表示可用的核心配额总计已达到上限。This indicates that the quota for total cores available to you has been reached.
  • 补救措施:请求操作员提供配额更高的附加计划。Remediation: Ask your operator for an add-on plan with additional quota. 编辑当前计划的配额不起作用,也不会反映提高的配额。Editing the current plan's quota will not work or reflect increased quota.
  • 发生次数:罕见Occurrence: Rare

特权终结点Privileged Endpoint

  • 适用于:此问题适用于 1910 和更低版本。Applicable: This issue applies to 1910 and earlier releases.
  • 原因:无法从运行非英语版 Windows 的计算机连接到特权终结点 (ERC VM)。Cause: Unable to connect to the Privileged Endpoint (ERC VMs) from a computer running a non-English version of Windows.
  • 补救措施:这是一个已知问题,已在 1910 以上的版本中修复。Remediation: This is a known issue that has been fixed in releases later than 1910. 解决方法之一是,使用 en-US 区域性运行 New-PSSession 和 Enter-PSSession Powershell cmdlet;有关示例,请使用以下脚本来设置区域性: https://resources.oreilly.com/examples/9780596528492/blob/master/Use-Culture.ps1As a workaround you can run the New-PSSession and Enter-PSSession PowerShell cmdlets using the en-US culture; for examples, set the culture using this script: https://resources.oreilly.com/examples/9780596528492/blob/master/Use-Culture.ps1.
  • 发生次数:罕见Occurrence: Rare

虚拟机规模集Virtual machine scale set

在 4 节点的 Azure Stack Hub 环境中进行修补和更新时出现故障Create failures during patch and update on 4-node Azure Stack Hub environments

  • 适用于:此问题适用于所有支持的版本。Applicable: This issue applies to all supported releases.
  • 原因:在包含 3 个容错域的可用性集中创建 VM 以及创建虚拟机规模集实例失败,在一个 4 节点 Azure Stack Hub 环境中进行更新时出现 FabricVmPlacementErrorUnsupportedFaultDomainSize 错误。Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
  • 补救措施:可以在包含 2 个容错域的可用性集中成功创建单一 VM。Remediation: You can create single VMs in an availability set with 2 fault domains successfully. 但是,在 4 节点 Azure Stack Hub 部署中进行更新时,仍然不能创建规模集实例。However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

ArchiveArchive

若要访问旧版本的已存档已知问题,请使用左侧目录上方的版本选择器下拉列表,然后选择要查看的版本。To access archived known issues for an older version, use the version selector dropdown above the table of contents on the left, and select the version you want to see.

后续步骤Next steps