For the most up-to-date instructions for applying Azure Stack Hub software updates, see Install Azure Stack Hub Updates.
Note: For the duration of the update process, alerts can appear in the Administration Portal. Normally, these can be ignored and they close automatically after the update installation finishes. As a best practice, we recommend that you log out of the Administration Portal after the job starts, and then monitor the progress through PowerShell. Leaving the Administration Portal open can delay the completion process and cause issues that require logging a ticket with Microsoft Azure Stack Support.
Monitoring Azure Stack Hub through PEP
For more information, see Monitor updates in Azure Stack Hub using the privileged endpoint.
This is an example of querying the update status using the PEP:
$cred = Get-Credential
$pepsession = New-PSSession -ComputerName xxx.xxx.xxx.xxx -ConfigurationName PrivilegedEndpoint -Credential $cred
$log = Invoke-Command -Session $pepSession -ScriptBlock { Get-AzureStackUpdateVerboseLog }
$log > ".\UpdateVerboseLog2.txt"
get-content UpdateVeboseLog.txt -Tail 24
After the installation finishes, to validate the status of the Azure Stack Hub and resolve any post-installation issues, run Test-AzureStack -Group UpdateReadiness from the PEP.
Notes
- If one or more of the validation tests return a failed status, resolve these issues before applying any updates. If required, log a ticket with Microsoft Azure Stack Hub Support.
- Repetitive running of the Test-AzureStack command can cause the update process to stall. Minimize the number of times that you run Test-AzureStack during a single update process.
- The virtual machines (VMs) used for DC01, DC02, ERCS1, ERCS2, and ERCS3 are pinned to specific scale unit nodes and do not move when each node is being drained. If the Azure Stack Hub operator is using a specific ERCS instance for the PEP session, they might need to create another ERCS session when the hosting node is placed into Maintenance mode.
