You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article discusses common issues in the Red Hat Update Infrastructure (RHUI) that are caused by expired or missing Transport Layer Security (TLS) or Secure Sockets Layer (SSL) certificates.
18
20
19
21
## Prerequisites
@@ -154,12 +156,12 @@ Use the following table to determine the correct RHUI package type based on your
154
156
| Image type | Support model | Applicable version | RHUI package prefix | Using `releasever`? |
##### <aid="eus"></a> EUS RHUI package installation
@@ -252,6 +255,41 @@ Select the tab of an EUS image type to see the corresponding instructions.
252
255
sudo rhel9-eus.config
253
256
```
254
257
258
+
###### [RHEL 10.x - EUS](#tab/rhel10-eus)
259
+
260
+
261
+
262
+
1. Create a config file by using this command:
263
+
264
+
```bash
265
+
sudo tee rhel10-eus.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-eus]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-eus)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-eus\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
266
+
267
+
```
268
+
269
+
2. Install the `rhui-azure-rhel10-eus` package by running.
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `dnf repolist` command:
282
+
283
+
```bash
284
+
sudo dnf repolist all
285
+
```
286
+
287
+
5. Remove the temp file created on step 1.
288
+
289
+
```bash
290
+
sudo rhel10-eus.config
291
+
```
292
+
255
293
---
256
294
257
295
@@ -818,6 +856,123 @@ The following steps apply if the OS version is *earlier than the latest version
818
856
---
819
857
820
858
859
+
> [!NOTE]
860
+
> If you're using a proxy in*/etc/yum.conf* or */etc/dnf.conf*, the `yum --config rhelX-XX-XX.config`command won't work because it doesn't include your proxy settings. In this case, move the temp file `rhelX-XX-XX.config` directly in`/etc/yum.repos.d/` as `.repo`
The following steps apply if the OS version is *earlier than the latest version that's available* that's supported by SAP for`RHEL 10.0`, and if the VM was created by using the `RHEL-SAP-APPS` offer image.
876
+
877
+
1. Create a config file by using this command:
878
+
879
+
```bash
880
+
sudo tee rhel10-sapapps.config > /dev/null <<<$'[rhui-microsoft-azure-rhel10-sapapps]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-sapapps)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-sapapps\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
881
+
```
882
+
883
+
2. Install the `rhui-azure-rhel10-sapapps` package by running the `dnf install` command:
The following steps apply if the OS version is *earlier than the latest version available* that's supported by SAP for`RHEL 10.0`, and if the VM was created by using the `RHEL-SAP-HA` offer image.
910
+
911
+
1. Create a config file by using this command:
912
+
913
+
```bash
914
+
sudo tee rhel10-sap-ha.config > /dev/null <<<$'[rhui-microsoft-azure-rhel10-sap-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-sap-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-sap-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
915
+
```
916
+
917
+
2. Install the `rhui-azure-rhel10-sap-ha` package by running the `dnf install` command:
sudo tee rhel10-ha.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
947
+
```
948
+
949
+
2. Install the `rhui-azure-rhel10-ha` package by running the [dnf](https://dnf.readthedocs.io/en/latest/command_ref.html) installation command:
3. Lock the `releasever` level. Currently, the version must be 10.0.
956
+
957
+
```bash
958
+
sudo sh -c 'echo 10.0 > /etc/dnf/vars/releasever'
959
+
```
960
+
961
+
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `dnf repolist` command:
962
+
963
+
```bash
964
+
sudo dnf repolist
965
+
```
966
+
967
+
5. Remove the temp file created on step 1.
968
+
969
+
```bash
970
+
sudo rm rhel10-ha.config
971
+
```
972
+
973
+
---
974
+
975
+
821
976
> [!NOTE]
822
977
> If you're using a proxy in*/etc/yum.conf* or */etc/dnf.conf*, the `yum --config rhelX-XX-XX.config`command won't work because it doesn't include your proxy settings. In this case, move the temp file `rhelX-XX-XX.config` directly in`/etc/yum.repos.d/` as `.repo`
823
978
>
@@ -929,5 +1084,3 @@ Revert the cryptography to the `DEFAULT` system policy setting by following thes
929
1084
For more information about cryptographic policy, see [Strong crypto defaults in RHEL 8 and deprecation of weak crypto algorithms](https://access.redhat.com/articles/3642912).
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/yum-dnf-common-issues.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ ms.date: 07/10/2025
18
18
19
19
**Applies to:**:heavy_check_mark: Linux VMs
20
20
21
+
## Summary
22
+
21
23
This article discusses and resolves common issues that you might experience when you use `yum` and `dnf` package management tools to install or update applications on Microsoft Azure virtual machines (VMs).
22
24
23
25
> [!CAUTION]
@@ -410,34 +412,36 @@ If the error typically occurs because an incorrect value is used for */etc/yum/v
410
412
411
413
2. Determine the current value for the release version by running the following `cat` command.
| RHEL 8, and 10|`sudo cat /etc/dnf/vars/releasever`|
417
419
418
420
3. Modify and use the correct value for the release version:
419
421
420
422
- If your system is using EUS repositories, make sure that the appropriate version lock is applied. In the following example, the version lock is added for RHEL 9.2 because `RHUI EUS` repositories are used:
421
423
422
424
```bash
423
425
sudo sh -c 'echo 9.2 > /etc/dnf/vars/releasever'
426
+
sudo sh -c 'echo 9.6 > /etc/dnf/vars/releasever'
424
427
```
425
428
426
429
> [!NOTE]
427
-
> Support forRHEL7 EUS ended on August 30, 2021. We recommend that you no longer use EUS repositoriesinRHEL7.
430
+
> Support forRHEL 7 EUS ended on August 30, 2021. We recommend that you no longer use EUS repositoriesinRHEL 7.
428
431
>
429
-
> RHEL 8._x_ versions forEUS are available. These versions include RHEL 8.8, 8.6, 8.4, 8.2, and 8.1.
432
+
>Support forRHEL 8EUS ended on May 31, 2025. RHEL 8.10 is the last planned minor release of RHEL 8 and is still supported, but isn't an EUS release. We recommend that you no longer use EUS repositoriesin RHEL 8 and instead switch to the non-EUS repos.
430
433
>
431
-
> RHEL 9._x_ versions for EUS are available. Currently, these versions include RHEL 9.2 and 9.0.
434
+
> RHEL 9._x_ versions for EUS are available. Currently, these versions include RHEL 9.6 and 9.4.
432
435
>
436
+
> RHEL 10._x_ versions for EUS are available. Currently, these versions include only RHEL 10.0.
433
437
> For more information about version availability, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
434
438
435
439
- If your system is using non-EUS repositories, make sure that you remove the version lock for the */etc/yum/vars/releasever* or */etc/dnf/vars/releasever* file by running the following command.
Copy file name to clipboardExpand all lines: support/windows-365/provisioning-errors.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Troubleshoot provisioning errors
3
3
description: Troubleshoot provisioning errors in Windows 365.
4
4
manager: dcscontentpm
5
-
ms.date: 01/7/2026
5
+
ms.date: 01/23/2026
6
6
ms.topic: troubleshooting
7
7
ms.reviewer: mattsha, erikje, mmoyaaceves
8
8
ms.custom:
@@ -173,6 +173,8 @@ If you receive this error, some factors to consider are:
173
173
174
174
If you encounter other provisioning errors not covered previously, make sure all the [required endpoints](/windows-365/enterprise/requirements-network?tabs=enterprise%2Cent#allow-network-connectivity) are allowed on the virtual network used for your ANC and any gateway device.
175
175
176
+
For more information about provisioning statuses, see [Device management overview for Cloud PCs](/windows-365/enterprise/device-management-overview).
177
+
176
178
## Next steps
177
179
178
180
[Troubleshooting Windows 365 issues](/windows-365/enterprise/troubleshooting).
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments