Category: Hotfix

Applies to: Azure Stack Integrated Systems

Summary

This update for Azure Stack version 1905 includes fixes to storage and compute services. No new features are being introduced in this update.

Important changes include the following:

• Fixed issue: Queue message expiration due to time skew in storage service.
• Fixed issue: User image creation and deletion operations fail if an image is in a failed state. 

Symptoms

• Queue messages: Messages in a queue will expire immediately after creation and tagged for garbage collection. This issue may present in three cases:
  • Retrieval of resources in Azure Resource Manager will fail.
  • Usage metric data is not collected and uploaded for processing.
  • Customer developed applications will fail to retrieve messages.
• User image management: Failed user image creation will put the user image service into a bad state.
  • New image creation will fail once the service is in this state.
  • Deletion of image may fail with the following error “Error: An internal disk management error occurred.”
    

Cause

• Queue message: Time skew in one of the instances running the table service will cause all subsequent messages to set to a fixed creation date. After 7 days (the default a expiration time for a message), the service will consider the message expired and tag it for garbage collection. 
• User image management: Due to the failed image creation, the user image manager does not have sufficient data in its repository to delete the image.

Hotfix information

To apply this hotfix, you must have version 1.1905.0.40 installed.

Important As outlined in the Release Notes for the 1905 update, make sure that you refer to the update activity checklist on running Test-AzureStack (with specified parameters), and resolve any operational issues that are found, including all warnings and failures. Also, review active alerts and resolve any that require action.

File information

How to get this update

Download the following files. Then, follow the instructions on the Apply updates in Azure Stack page on the Microsoft Docs website to apply this update to Azure Stack.

Download the file now.
Download the hotfix .xml file now.

Applies to: Azure Stack integrated systems

Summary

This update for Azure Stack version 1904 includes fixes and reliability improvements. No new features are being introduced in this update.

Important changes include the following:

• Fixed issue: Compute host agent warning appears after restarting a node in the scale unit. 
• Fixed issue: Infrastructure backup fails to back up internal identity service. 
  
• Improved reliability of Update Resource provider automatic downloader.

Symptoms

• Compute host agent: Warning appears after restarting a node in the scale unit. 
• Identity service backup: Infrastructure backup finishes but is only partially successful because it does not back up the internal identity service.

Cause

• Compute host agent: Restarting the node changes the default startup setting for the compute host agent service.
• Identity service backup: There is a bug in the backup workflow.
  

Hotfix information

To apply this hotfix, you must have version 1.1904.0.36 installed.

Important! As outlined in the Release Notes for the 1904 update, make sure that you refer to the update activity checklist on running Test-AzureStack (with specified parameters), and resolve any operational issues that are found, including all warnings and failures. Also, review active alerts and resolve any that require action.

File information

How to get this update

Download the following files. Then, follow the instructions on the Apply updates in Azure Stack page on the Microsoft Docs website to apply this update to Azure Stack.

Download the file now.
Download the hotfix .xml file now.

Applies to: Azure Stack Integrated Systems

Summary

This update for Azure Stack version 1903 includes reliability improvements. No new features are being introduced in this update. Important changes include the following:

• Fix time out issue during stop-deallocate of IaaS VMs with multiple large managed disks.
• Increase VM uptime when a system is updating.
• Fix issues with resource exhaustion when the system is running at scale improving overall system stability. 
• Update to Windows Defender engine to address issues with storage availability.  
  

Duration
The installation of this Hotfix took us about 1 hour and 10 minutes on a twelve node Azure Stack.

Symptoms

• IaaS VM with multiple large managed disks: During stop-deallocate, the operation fails due to time out. 
• VM uptime during system updates: Azure Stack updates perform a rolling update of the scale-unit by draining one node at a time and updating it. During node drain, the goal is to evacuate a node with no perceived downtime to the VM. However, if the network is under heavy load, VMs may incur a brownout or a blackout.  
• Resource exhaustion: When a system is running at scale, internal processes may exhaust platform resources resulting in failed operations in the portal. 
• Windows Defender: Issues in the Windows Defender engine impact the availability of storage.  

Cause

• IaaS VM with multiple large managed disks: Missing information in CRP impacts the stop-deallocate operation. 
• VM uptime during system updates: Number of concurrent VMs evacuate and bandwidth consumed is too high. 
• Resource exhaustion: Sub-optimal Throttling of resource allocation for process execution. 
• Windows Defender: Stability issues identified in the Windows Defender engine in this release.
  

Resolution

• IaaS VM with multiple large managed disks: Fix in CRP to address the time out. 
• VM uptime during system updates: Reduce the number of VMs evacuated concurrently and place a cap on bandwidth consumed. 
• Resource exhaustion: Optimize resource throttling. 
• Windows Defender: Update Windows Defender engine version. 
  

Hotfix information

To apply this hotfix, you must have version 1.1903.0.35 installed.

Important!
As outlined in the Release Notes for the 1903 update, be sure to follow the instructions in the Prerequisites section on running Test-AzureStack (with specified parameters) and resolve any operational issues found, including all warnings and failures. Also review active alerts and resolve any that require action.

File information

How to get this update

Download the following files. As soon as the files have been downloaded, follow the instructions on the Apply updates in Azure Stack page on the Microsoft Docs website to apply this update to Azure Stack.Download the hotfix .zip file now.

Download the hotfix .xml file now.

More information

Azure Stack update resources

Manage updates in Azure Stack overview

Apply updates in Azure Stack

Monitor updates in Azure Stack by using the privileged endpoint