|
2 | 2 | title: Troubleshoot known issues with Azure Update Manager
|
3 | 3 | description: This article provides details on known issues and how to troubleshoot any problems with Azure Update Manager.
|
4 | 4 | ms.service: azure-update-manager
|
5 |
| -ms.date: 09/06/2024 |
| 5 | +ms.date: 09/11/2024 |
6 | 6 | ms.topic: troubleshooting
|
7 | 7 | ms.author: sudhirsneha
|
8 | 8 | author: SnehaSudhirG
|
@@ -236,6 +236,105 @@ To find more information, review the logs in the file path provided in the error
|
236 | 236 |
|
237 | 237 | Set a longer time range for maximum duration when you're triggering an [on-demand update deployment](deploy-updates.md) to help avoid the problem.
|
238 | 238 |
|
| 239 | + |
| 240 | +### Windows/Linux OS update extension isn't installed |
| 241 | + |
| 242 | +#### Issue |
| 243 | + |
| 244 | +The Windows/Linux OS Update extension must be successfully installed on Arc machines to perform on-demand assessments, patching, and scheduled patching. |
| 245 | + |
| 246 | +#### Resolution |
| 247 | + |
| 248 | +Trigger an on-demand assessment or patching to install the extension on the machine. You can also attach the machine to a maintenance configuration schedule which will install the extension when patching is performed as per the schedule. |
| 249 | + |
| 250 | +If the extension is already present on the machine but the extension status is not **Succeeded**, ensure that you [remove the extension](../azure-arc/servers/manage-vm-extensions-portal.md#remove-extensions) and trigger an on-demand operation so that it is installed again. |
| 251 | + |
| 252 | +### Windows/Linux patch update extension isn't installed |
| 253 | + |
| 254 | +#### Issue |
| 255 | +The Windows/Linux patch update extension must be successfully installed on Azure machines to perform on-demand assessment or patching, scheduled patching and for periodic assessments. |
| 256 | + |
| 257 | +#### Resolution |
| 258 | +Trigger an on-demand assessment or patching to install the extension on the machine. You can also attach the machine to a maintenance configuration schedule which will install the extension when patching is performed as per the schedule. |
| 259 | + |
| 260 | +If the extension is already present on the machine but the extension status is not **Succeeded**, ensure that you [remove the extension](../azure-arc/servers/manage-vm-extensions-portal.md#remove-extensions) and trigger an on-demand operation which will install it again. |
| 261 | + |
| 262 | + |
| 263 | +### Allow Extension Operations check failed |
| 264 | + |
| 265 | +#### Issue |
| 266 | + |
| 267 | +The property [AllowExtensionOperations](https://learn.microsoft.com/dotnet/api/microsoft.azure.management.compute.models.osprofile.allowextensionoperations?view=azure-dotnet-legacy) is set to false in the machine OSProfile. |
| 268 | + |
| 269 | +#### Resolution |
| 270 | +The property should be set to true to allow extensions to work properly. |
| 271 | + |
| 272 | +### Sudo privileges not present |
| 273 | + |
| 274 | +#### Issue |
| 275 | + |
| 276 | +Sudo privileges are not granted to the extensions for assessment or patching operations on Linux machines. |
| 277 | + |
| 278 | +#### Resolution |
| 279 | +Grant sudo privileges to ensure assessment or patching operations succeed. |
| 280 | + |
| 281 | +### Proxy is configured |
| 282 | + |
| 283 | +#### Issue |
| 284 | + |
| 285 | +Proxy is configured on Windows or Linux machines that may block access to endpoints required for assessment or patching operations to succeed. |
| 286 | + |
| 287 | +#### Resolution |
| 288 | + |
| 289 | +For Windows, see [issues related to proxy](https://learn.microsoft.com/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting?toc=%2Fwindows%2Fdeployment%2Ftoc.json&bc=%2Fwindows%2Fdeployment%2Fbreadcrumb%2Ftoc.json#issues-related-to-httpproxy). |
| 290 | + |
| 291 | +For Linux, ensure proxy setup doesn't block access to repositories that are required for downloading and installing updates. |
| 292 | + |
| 293 | +### TLS 1.2 Check Failed |
| 294 | + |
| 295 | +#### Issue |
| 296 | + |
| 297 | +TLS 1.0 and TLS 1.1 are deprecated. |
| 298 | + |
| 299 | +#### Resolution |
| 300 | + |
| 301 | +Use TLS 1.2 or higher. |
| 302 | + |
| 303 | +For Windows, see [Protocols in TLS/SSL Schannel SSP](https://learn.microsoft.com/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp-). |
| 304 | + |
| 305 | +For Linux, execute the following command to see the supported versions of TLS for your distro. |
| 306 | +`nmap --script ssl-enum-ciphers -p 443 www.azure.com` |
| 307 | + |
| 308 | +### Https connection check failed |
| 309 | + |
| 310 | +#### Issue |
| 311 | + |
| 312 | +Https connection is not available which is required to download and install updates from required endpoints for each operating system. |
| 313 | + |
| 314 | +#### Resolution |
| 315 | + |
| 316 | +Allow Https connection from your machine. |
| 317 | + |
| 318 | +### MsftLinuxPatchAutoAssess service is not running, or Time is not active |
| 319 | + |
| 320 | +#### Issue |
| 321 | + |
| 322 | +[MsftLinuxPatchAutoAssess](https://github.com/Azure/LinuxPatchExtension) is required for successful periodic assessments on Linux machines. |
| 323 | + |
| 324 | +#### Resolution |
| 325 | + |
| 326 | +Ensure that the LinuxPatchExtension status is succeeded for the machine. Reboot the machine to check if the issue is resolved. |
| 327 | + |
| 328 | +### Linux repositories aren't accessible |
| 329 | + |
| 330 | +#### Issue |
| 331 | + |
| 332 | +The updates are downloaded from configured public or private repositories for each Linux distro. The machine is unable to connect to these repositories to download or assess the updates. |
| 333 | + |
| 334 | +#### Resolution |
| 335 | + |
| 336 | +Ensure that network security rules don’t hinder connection to required repositories for update operations. |
| 337 | + |
239 | 338 | ## Next steps
|
240 | 339 |
|
241 | 340 | * To learn more about Update Manager, see the [Overview](overview.md).
|
|
0 commit comments