Skip to main content

Known issues

The followings are known issues for ThinkAgile MX Solution Builder Extension. The known issues listed in this section are grouped by SBE Version. Click on the SBE version you installed to view the known issues.

Premier 4.1.2505.1070 / Standard 4.1.2505.1065​

Intel NIC E810 device driver v1.15.121.0 may cause Azure Local nodes to crash
Table 1. Intel NIC E810 device driver v1.15.121.0 may cause Azure Local nodes to crash
SBE versionThe known issue is applied for the following SBE versions:

  • ThinkAgileMXPremier: 4.1.2505.1070

  • ThinkAgileMXStandard: 4.1.2505.1065

  • ThinkAgileMXPremier: 4.1.2501.1021

  • ThinkAgileMXStandard: 4.1.2503.1002

Issue Description:This is a known Intel E810 Windows driver issue documented in their v30.0.1 Release Notes: https://downloadmirror.intel.com/849481/Intel_Ethernet_Controller_Products_Release_Notes_30.0.1.pdf 
Root cause:Installing Intel NIC E810 device driver v1.15.121.0 may cause crashes of vmswitch.sys in Azure Local cluster nodes
Workaround:Install Intel NIC E810 device driver v1.17.72.0
Fix:The next SBE release (July) will include the v1.17.72.0 Intel NIC E810 device driver 
CAU may fail because CSV inaccessible due to missing disks after HBA driver update
Table 2. CAU may fail because CSV inaccessible due to missing disks after HBA driver update
SBE versionThe known issue is applied for the following SBE versions:

  • ThinkAgileMXPremier: 4.1.2505.1070

  • ThinkAgileMXStandard: 4.1.2505.1065

  • ThinkAgileMXPremier: 4.1.2501.1021

  • ThinkAgileMXStandard: 4.1.2503.1002

Issue Description:HBA driver update may cause disks to disappear because of needing a reboot after driver install for disks to return
Root cause:SBE CAU plugin may fail when trying to write logs when CSV is inaccessible due disks missing before rebooting
Workaround:Perform reboot if safe for Azure Local cluster after updating HBA driver 
Fix:This issue will be patched in an upcoming SBE release 

Premier 4.1.2501.1021 / Standard 4.1.2503.1002​

OS Update Automatically Set to Run on 3rd Tuesday of Month
Table 3. OS Update Automatically Set to Run on 3rd Tuesday of Month
SBE versionThe known issue is applied for the following SBE versions:

  • ThinkAgileMXPremier: 4.1.2501.1021

  • ThinkAgileMXStandard: 4.1.2503.1002

Issue Description:This is a Microsoft known issue documented here: https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/OS-update-automatically-set-to-run-on-3rd-Tuesday-following-SBE-update.md
Root cause:

Prior to the 2505 release of Azure Local, the Solution Builder Extension (SBE) automation will remove the CauPluginName property from the CauClusterRole because the SBE uses a "custom" CAU plugin using the following syntax: Set-CauClusterRole -CauPluginName $null -Force

This was previously considered a best practice (to remove traces of custom plugins that shouldn't be used outside of SBE updates). However, it had the unintended effect of adding the DaysOfWeek and WeeksOfMonth attributes to the CauClusterRole. This occurred because any call to Set-CauClusterRole will add those settings by default.

Workaround:For immediate mitigation, please follow the recommended instructions from Microsoft: https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/OS-update-automatically-set-to-run-on-3rd-Tuesday-following-SBE-update.md#mitigation-details
Fix:

The dependency on Set-CauClusterRole has been removed in Standard package 4.1.2505.1065 and Premier package 4.1.2505.1070

SBE CAU run fails if QAT utility driver is missing
Table 4. SBE CAU run fails if QAT utility driver is missing
SBE versionThe known issue is applied for the following SBE versions:

  • ThinkAgileMXPremier: 4.1.2501.1021

  • ThinkAgileMXStandard: 4.1.2503.1002

Issue Description:SBE CAU fails On Intel Chipset update when missing QAT utility installation on MX650 V3/630 V3

Root cause:When customers re-image their servers on their own after receiving them from our factories, the systems will be missing necessary device drivers, notably the Intel QAT utility, that are built into the Lenovo OEM image with which our servers are shipped.
Workaround:If your Lenovo ThinkAgile MX servers were re-imaged and no longer contain the Lenovo OEM factory image, please manually install the QAT utility (intc-lnvgy_utl_chipset_inteldp.*.qat-*-*_windows_indiv) from our latest Best Recipe (https://support.lenovo.com/us/en/solutions/ht515442) before proceeding with SBE Updates.
Fix:This is working as designed for Lenovo ThinkAgile MX solutions that are shipped with the Lenovo OEM factory image.
SBE Update Test BMC Management IP Address Availability Health Check failure
Table 5. SBE Update Test BMC Management IP Address Availability Health Check failure
SBE versionThe known issue is applied for the following SBE versions:

  • ThinkAgileMXPremier: 4.1.2501.1021

  • ThinkAgileMXStandard: 4.1.2503.1002

Issue Description:SBE solution update fails on the Test BMC Management IP Address Availability Health Check failure Health Check with the following error (example shown in screenshot below):
  • “Error while running 'Get-SBEHealthCheckResultOnNode' on '*.*.*.*'. Exception message: Error running Get-SBEHealthCheckResultOnNode. Error: Testing connection to computer '*.*.*.*' failed: Error due to lack of resource”
Figure 1. Test BMC Management IP Address Availability Health Check failure

Root cause:XCC External IP is not reachable from cluster management subnet.
Workaround:Temporarily allow inbound connections from the XCC IP address to the cluster management node through the firewall for the duration of the SBE update.
Fix:This issue will be resolved in the upcoming SBE release in May/June 2025 release.