Merge pull request #8902 from MicrosoftDocs/main

Auto push to live 2025-05-12 02:32:50

Author: Deland-Han

support/azure/azure-kubernetes/create-upgrade-delete/cannot-scale-cluster-autoscaler-enabled-node-pool.md

@@ -3,14 +3,14 @@ title: Cluster autoscaler fails to scale with cannot scale cluster autoscaler en
 description: Learn how to troubleshoot the cannot scale cluster autoscaler enabled node pool error when your autoscaler isn't scaling up or down.
 author: sgeannina
 ms.author: ninasegares
-ms.date: 10/17/2023
-ms.reviewer: aritraghosh, chiragpa
+ms.date: 04/17/2025
+ms.reviewer: aritraghosh, chiragpa.momajed
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 ---
 # Cluster autoscaler fails to scale with "cannot scale cluster autoscaler enabled node pool" error
 
-This article discusses how to resolve the "cannot scale cluster autoscaler enabled node pool" error that appears when scaling a cluster with an autoscaler enabled node pool.
+This article discusses how to resolve the "cannot scale cluster autoscaler enabled node pool" error that occurs when you scale a cluster that has an autoscaler-enabled node pool.
 
 ## Symptoms
 
@@ -22,45 +22,75 @@ You receive an error message that resembles the following message:
 
 ## Troubleshooting checklist
 
-Azure Kubernetes Service (AKS) uses virtual machine scale sets-based agent pools, which contain cluster nodes and [cluster autoscaling capabilities](/azure/aks/cluster-autoscaler) if enabled.
+Azure Kubernetes Service (AKS) uses Azure Virtual Machine Scale Sets-based agent pools. These pools contain cluster nodes and [cluster autoscaling capabilities](/azure/aks/cluster-autoscaler), if they're enabled.
 
 ### Check that the cluster virtual machine scale set exists
 
-1. Sign in to [Azure portal](https://portal.azure.com).
-1. Find the node resource group by searching the following names:
-
-   - The default name `MC_{AksResourceGroupName}_{YourAksClusterName}_{AksResourceLocation}`.
-   - The custom name (if it was provided at creation).
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Find the node resource group by searching for the following names:  
 
+   - The default name `MC_{AksResourceGroupName}_{YourAksClusterName}_{AksResourceLocation}`
+   - The custom name (if it was provided at creation)
+     >
    > [!NOTE]
-   > When you create a new cluster, AKS automatically creates a second resource group to store the AKS resources. For more information, see [Why are two resource groups created with AKS?](/azure/aks/faq#why-are-two-resource-groups-created-with-aks)
+   > When you create a cluster, AKS automatically creates a second resource group to store the AKS resources. For more information, see [Why are two resource groups created with AKS?](/azure/aks/faq#why-are-two-resource-groups-created-with-aks)
 
-1. Check the list of resources and make sure that there's a virtual machine scale set.
+1. Check the list of resources to make sure that a virtual machine scale set exists.
 
 ## Cause 1: The cluster virtual machine scale set was deleted
 
-Deleting the virtual machine scale set attached to the cluster causes the cluster autoscaler to fail. It also causes issues when provisioning resources such as nodes and pods.
+If you delete the virtual machine scale set that's attached to the cluster, this action causes the cluster autoscaler to fail. It also causes issues when you provision resources such as nodes and pods.
 
 > [!NOTE]
-> Modifying any resource under the node resource group in the AKS cluster is an unsupported action and will cause cluster operation failures. You can prevent changes from being made to the node resource group by [blocking users from modifying resources](/azure/aks/cluster-configuration#fully-managed-resource-group-preview) managed by the AKS cluster.
+> Modifying any resource under the node resource group in the AKS cluster is an unsupported action and causes cluster operation failures. You can prevent changes from being made to the node resource group by [blocking users from modifying resources](/azure/aks/cluster-configuration#fully-managed-resource-group-preview) that are managed by the AKS cluster.
+
+### Reconcile node pool
+
+If the cluster virtual machine scale set is accidentally deleted, you can reconcile the node pool by using `az aks nodepool update`:
+
+```bash
+# Update Node Pool Configuration
+az aks nodepool update --resource-group <resource-group-name> --cluster-name <cluster-name> --name <nodepool-name> --tags <tags> --node-taints <taints> --labels <labels>
+
+# Verify the Update
+az aks nodepool show --resource-group <resource-group-name> --cluster-name <cluster-name> --name <nodepool-name>
+```
+Monitor the node pool to make sure that it's functioning as expected and that all nodes are operational.
 
 ## Cause 2: Tags or any other properties were modified from the node resource group
 
-You may receive scaling errors if you modify or delete Azure-created tags and other resource properties in the node resource group. For more information, see [Can I modify tags and other properties of the AKS resources in the node resource group?](/azure/aks/faq#can-i-modify-tags-and-other-properties-of-the-aks-resources-in-the-node-resource-group)
+You may experience scaling errors if you modify or delete Azure-created tags and other resource properties in the node resource group. For more information, see [Can I modify tags and other properties of the AKS resources in the node resource group?](/azure/aks/faq#can-i-modify-tags-and-other-properties-of-the-aks-resources-in-the-node-resource-group)
+
+### Reconcile node resource group tags
+
+Use the Azure CLI to make sure that the node resource group has the correct tags for AKS name and the AKS group name:
+
+```bash
+# Add or update tags for AKS name and AKS group name
+az group update --name <node-resource-group-name> --set tags.AKS-Managed-Cluster-Name=<aks-managed-cluster-name> tags.AKS-Managed-Cluster-RG=<aks-managed-cluster-rg>
+
+# Verify the tags
+az group show --name <node-resource-group-name> --query "tags"
+```
+Monitor the resource group to make sure that the tags are correctly applied and that the resource group is functioning as expected.
 
 ## Cause 3: The cluster node resource group was deleted
 
-Deleting the cluster node resource group causes issues when provisioning the infrastructure resources required by the cluster, which causes the cluster autoscaler to fail.
+Deleting the cluster node resource group causes issues when you provision the infrastructure resources that are required by the cluster. This action causes the cluster autoscaler to fail.
 
 ## Solution: Update the cluster to the goal state without changing the configuration
 
-To resolve this issue, you can run the following command to recover the deleted virtual machine scale set or any tags (missing or modified):
+To resolve this issue, run the following command to recover the deleted virtual machine scale set or any tags (missing or modified).
 
 > [!NOTE]
-> It might take a few minutes until the operation completes.
+> It might take a few minutes until the operation finishes.
 
 ```azurecli
 az aks update --resource-group <resource-group-name> --name <aks-cluster-name>
 ```
 
+### Additional troubleshooting tips
+
+- Check the Azure Activity Log for any recent changes or deletions.
+
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md

@@ -1,10 +1,10 @@
 ---
 title: Troubleshoot connectivity and registration for SUSE SLES VMs
 description: Troubleshoot scenarios in which an Azure VM that has a SUSE Linux Enterprise Server image can't connect to the SUSE Subscription Management Tool (SMT) repository.
-ms.date: 02/26/2025
+ms.date: 05/12/2025
 author: rnirek
 ms.author: hokamath
-ms.reviewer: adelgadohell, mahuss, esanchezvela, scotro, v-weizhu, divargas
+ms.reviewer: adelgadohell, mahuss, esanchezvela, scotro, v-weizhu, divargas, vkchilak
 editor: v-jsitser
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
@@ -219,7 +219,7 @@ If instances aren't regularly updated, they can become incompatible with our upd
 3. Download the following packages:
 
     ```bash
-    sudo zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin libsuseconnect suseconnect-ruby-bindings docker libcontainers-common
+    sudo zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin libsuseconnect suseconnect-ruby-bindings docker libcontainers-common containerd libcontainers-sles-mounts runc
     ```
 4. Run the following commands:
 

support/sql/analysis-services/cannot-connect-named-instance.md

@@ -1,15 +1,15 @@
 ---
 title: Can't connect to a named instance
 description: This article provides resolutions where you might not be able to connect to a named instance of Analysis Services that is installed on a failover cluster.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Analysis Services
-ms.reviewer: karang
+ms.reviewer: karang, gasadas
 ---
 # Cannot connect to a named instance of a clustered analysis service
 
 This article helps you resolve the problem where you might not be able to connect to a named instance of Analysis Services that is installed on a failover cluster.
 
-_Original product version:_   SQL Server 2008 R2 Enterprise, SQL Server 2008 Enterprise, Microsoft SQL Server 2005 Enterprise Edition  
+_Original product version:_   SQL Server    
 _Original KB number:_   2429685
 
 ## Symptoms
@@ -27,14 +27,13 @@ You might not able to connect to a named instance of Analysis Services that is i
 ## Cause
 
 The problem occurs when you start the named instance of SQL Server Analysis services (SSAS) using either SQL Server Configuration Manager or the Services applet in the Control panel.
-When you start an SSAS instance on a failover cluster using a tool other than Failover Cluster Management (Cluster administrator on older Operating Systems), that SSAS instance will run as a stand-alone instance and will listen on a non-default port resulting in connection failures from various applications.
+When you start an SSAS instance on a failover cluster using a tool other than Failover Cluster Management (Cluster administrator on older Operating Systems), that SSAS instance will run as a stand-alone instance and will listen on a nondefault port resulting in connection failures from various applications.
 
 ## Resolution
 
 Stop and restart the SQL Server Analysis services using the Failover Cluster Management tool.
 
 ## More information
 
-An SSAS instance started on a cluster (default or named instance) will start listening on all IP addresses of the cluster group using the default port of 2383. The server setting `<Port>` property does not change the port number of SSAS service on a cluster.
+An SSAS instance started on a cluster (default or named instance) will start listening on all IP addresses of the cluster group using the default port of 2383. The server setting `<Port>` property doesn't change the port number of SSAS service on a cluster.
 
-For more information, see the KB article: [How to determine and change the port of an SSAS Instance](https://support.microsoft.com/help/2466860)

support/sql/analysis-services/writeback-performance-issue-cell-security-enable.md

@@ -1,27 +1,27 @@
 ---
 title: Writeback performance issue
 description: This article provides workarounds for the writeback performance problem that occurs when cell security is enabled in SQL Server Analysis Services.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Analysis Services
-ms.reviewer: haidongh, heidist
+ms.reviewer: haidongh, heidist, gasadas
 ---
 # Writeback performance problem when cell security is enabled in SQL Server Analysis Services
 
 This article helps you work around the writeback performance problem that occurs when cell security is enabled in SQL Server Analysis Services.
 
-_Original product version:_   SQL Server 2012 Analysis Services  
+_Original product version:_   SQL Server 2012 Analysis Services and later versions  
 _Original KB number:_   2747616
 
 ## Symptoms
 
-Assume that you are running Microsoft SQL Server Analysis Services (SSAS) under a role for which cell security is enabled. When you try to execute an UPDATE CUBE Multidimensional Expressions (MDX) statement, the statement execution may take longer to execute than for a role for which cell security is not enabled.
+Assume that you're running Microsoft SQL Server Analysis Services (SSAS) under a role for which cell security is enabled. When you try to execute an UPDATE CUBE Multidimensional Expressions (MDX) statement, the statement execution may take longer to execute than for a role for which cell security isn't enabled.
 
 ## Cause
 
 This behavior is by design. When cell security is enabled, the Analysis Services engine executes the queries in cell-by-cell mode. If the writeback operation performs allocation at a high level, the space of leaf level cells will be large.
 
 > [!NOTE]
-> The space is not the number of rows in the fact table. The space is the full cross join space of all dimension granularity attributes. It takes a long time to enumerate those cells one-by-one in order to check the cell security.
+> The space isn't the number of rows in the fact table. The space is the full cross join space of all dimension granularity attributes. It takes a long time to enumerate those cells one-by-one in order to check the cell security.
 
 ## Workaround
 
@@ -36,7 +36,7 @@ To work around this issue, use one of the following methods.
 
 - Method 2  
 
-    Perform the writeback operation at the lowest granularity level of a certain member. You cannot allocate for many detailed granularity members.
+    Perform the writeback operation at the lowest granularity level of a certain member. You can't allocate for many detailed granularity members.
 
     > [!NOTE]
     > You may have to create dummy members in dimension tables that are marked as adjustment members in each dimension, to support the writeback operation.

support/sql/analytics-platform-system/detect-data-skew-distribution-key-values.md

@@ -1,15 +1,16 @@
 ---
 title: Detect skew on distribution key values
 description: This article describes how to detect skew on the distribution key of a distributed table in a Parallel Data Warehouse appliance.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Parallel Data Warehouse (APS)
 ms.topic: how-to
+ms.reviewer: jopilov, ccaldera
 ---
 # Detect data skew on the distribution key values
 
 This article shows how to detect skew on the distribution key of a distributed table in a Parallel Data Warehouse appliance.
 
-_Original product version:_   SQL Server 2008 R2 Parallel Data Warehouse  
+_Original product version:_   SQL Server Parallel Data Warehouse  
 _Original KB number:_   3046863
 
 ## Summary
@@ -29,9 +30,9 @@ order by count(distribtuion_key) desc
 ```
 
 > [!NOTE]
-> The `having` clause is commented out. However, if you want to perform a quick check of whether there is significant skew, this clause may tell you. You may have to adjust the having value to something that makes sense for your result set. For example, if all values have 5,000 records, we recommend that you set this value to 7,500 or 10,000 to indicate an issue.
+> The `having` clause is commented out. However, if you want to perform a quick check of whether there's significant skew, this clause may tell you. You may have to adjust the having value to something that makes sense for your result set. For example, if all values have 5,000 records, we recommend that you set this value to 7,500 or 10,000 to indicate an issue.
 
-The question of when skew becomes a problem does not have a deterministic answer. Skew becomes a problem when performance of skewed distributions becomes noticeable and the application cannot tolerate the situation. The rule of thumb is that the appliance can tolerate a skew of 10 to 20 percent across all the tables. Within this threshold, the skewed distributions should even out under concurrency. Above this threshold, you may start to see some long-running distributions when the data is processed. Some implementations may be able to tolerate greater skew, and some implementations may be unable to tolerate this much. Testing is required to determine the actual threshold for your implementation.
+The question of when skew becomes a problem doesn't have a deterministic answer. Skew becomes a problem when performance of skewed distributions becomes noticeable and the application can't tolerate the situation. The rule of thumb is that the appliance can tolerate a skew of 10 to 20 percent across all the tables. Within this threshold, the skewed distributions should even out under concurrency. Above this threshold, you may start to see some long-running distributions when the data is processed. Some implementations may be able to tolerate greater skew, and some implementations may be unable to tolerate this much. Testing is required to determine the actual threshold for your implementation.
 
 ## More information
 

support/sql/analytics-platform-system/error-cetas-to-blob-storage.md

@@ -1,15 +1,15 @@
 ---
 title: Error 105005 when you do CETAS to blob storage
 description: This article provides resolutions for the error that occurs when you do a CETAS operation to Azure Blob storage by using PolyBase.
-ms.date: 08/05/2020
+ms.date: 05/09/2025
 ms.custom: sap:Parallel Data Warehouse (APS)
-ms.reviewer: daleche, christys
+ms.reviewer: daleche, christys, ccaldera
 ---
 # Error 105005 when you do CETAS operation to Azure blob storage
 
 This article helps you resolve the problem that occurs when you do a `CREATE EXTERNAL TABLE AS SELECT (CETAS)` operation to Azure Blob storage by using PolyBase.
 
-_Original product version:_   SQL Server 2012 Parallel Data Warehouse (APS), SQL Server 2008 R2 Parallel Data Warehouse  
+_Original product version:_   SQL Server Parallel Data Warehouse (APS)   
 _Original KB number:_   3210540
 
 ## Symptoms