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
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/redhat/redhat-rhui.md
+37-34Lines changed: 37 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,35 +40,35 @@ Information on Red Hat support policies for all versions of RHEL can be found on
40
40
41
41
As of April 2019, Azure offers RHEL images that are connected to Extended Update Support (EUS) repositories by default and RHEL images that come connected to the regular (non-EUS) repositories by default. More details on RHEL EUS are available in Red Hat's [version lifecycle documentation](https://access.redhat.com/support/policy/updates/errata) and [EUS documentation](https://access.redhat.com/articles/rhel-eus). The default behavior of `sudo yum update` will vary depending which RHEL image you provisioned from, as different images are connected to different repositories.
42
42
43
-
For a full image list, run `az vm image list --publisher redhat --all` using the Azure CLI.
43
+
For a full image list, run `az vm image list --offer RHEL --all -p RedHat --output table` using the Azure CLI.
44
44
45
45
### Images connected to non-EUS repositories
46
46
47
47
If you provision a VM from a RHEL image that is connected to non-EUS repositories, you will be upgraded to the latest RHEL minor version when you run `sudo yum update`. For example, if you provision a VM from an RHEL 7.4 PAYG image and run `sudo yum update`, you end up with an RHEL 7.8 VM (the latest minor version in the RHEL7 family).
48
48
49
49
Images that are connected to non-EUS repositories will not contain a minor version number in the SKU. The SKU is the third element in the URN (full name of the image). For example, all of the following images come attached to non-EUS repositories:
50
50
51
-
```text
52
-
RedHat:RHEL:7-LVM:7.4.2018010506
53
-
RedHat:RHEL:7-LVM:7.5.2018081518
54
-
RedHat:RHEL:7-LVM:7.6.2019062414
55
-
RedHat:RHEL:7-RAW:7.4.2018010506
56
-
RedHat:RHEL:7-RAW:7.5.2018081518
57
-
RedHat:RHEL:7-RAW:7.6.2019062120
51
+
```output
52
+
RedHat:RHEL:7-LVM:7.9.2023032012
53
+
RedHat:RHEL:8-LVM:8.7.2023022813
54
+
RedHat:RHEL:9-lvm:9.1.2022112101
55
+
RedHat:rhel-raw:7-raw:7.9.2022040605
56
+
RedHat:rhel-raw:8-raw:8.6.2022052413
57
+
RedHat:rhel-raw:9-raw:9.1.2022112101
58
58
```
59
59
60
-
Note that the SKUs are either 7-LVM or 7-RAW. The minor version is indicated in the version (fourth element in the URN) of these images.
60
+
Note that the SKUs are either X-LVM or X-RAW. The minor version is indicated in the version (fourth element in the URN) of these images.
61
61
62
62
### Images connected to EUS repositories
63
63
64
64
If you provision a VM from a RHEL image that is connected to EUS repositories, you will not be upgraded to the latest RHEL minor version when you run `sudo yum update`. This is because the images connected to EUS repositories are also version-locked to their specific minor version.
65
65
66
66
Images connected to EUS repositories will contain a minor version number in the SKU. For example, all of the following images come attached to EUS repositories:
67
67
68
-
```text
69
-
RedHat:RHEL:7.4:7.4.2019062107
70
-
RedHat:RHEL:7.5:7.5.2019062018
71
-
RedHat:RHEL:7.6:7.6.2019062116
68
+
```output
69
+
RedHat:RHEL:7_9:7.9.20230301107
70
+
RedHat:RHEL:8_7:8.7.2023022801
71
+
RedHat:RHEL:9_1:9.1.2022112113
72
72
```
73
73
74
74
## RHEL EUS and version-locking RHEL VMs
@@ -83,6 +83,9 @@ At the time of this writing, EUS support has ended for RHEL <= 7.4. See the "Red
83
83
* RHEL 7.5 EUS support ends April 30, 2020
84
84
* RHEL 7.6 EUS support ends May 31, 2021
85
85
* RHEL 7.7 EUS support ends August 30, 2021
86
+
* RHEL 8.4 EUS support ends May 31, 2023
87
+
* RHEL 8.6 EUS support ends May 31, 2024
88
+
* RHEL 9.0 EUS support ends May 31, 2024
86
89
87
90
### Switch a RHEL VM 7.x to EUS (version-lock to a specific minor version)
88
91
Use the following instructions to lock a RHEL 7.x VM to a particular minor release (run as root):
@@ -91,17 +94,17 @@ Use the following instructions to lock a RHEL 7.x VM to a particular minor relea
91
94
> This only applies for RHEL 7.x versions for which EUS is available. At the time of this writing, this includes RHEL 7.2-7.7. More details are available at the [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata) page.
@@ -118,28 +121,28 @@ Use the following instructions to lock a RHEL 8.x VM to a particular minor relea
118
121
> This only applies for RHEL 8.x versions for which EUS is available. At the time of this writing, this includes RHEL 8.1-8.2. More details are available at the [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata) page.
> The above instruction will lock the RHEL minor release to the current minor release. Enter a specific minor release if you are looking to upgrade and lock to a later minor release that is not the latest. For example, `echo 8.1 > /etc/yum/vars/releasever` will lock your RHEL version to RHEL 8.1.
141
144
>[!NOTE]
142
-
> If there are permission issues to access the releasever, you can edit the file using 'nano /etc/yum/vars/releaseve'and add the image version details and save ('Ctrl+o'then press enter and then'Ctrl+x').
145
+
> If there are permission issues to access the releasever, you can edit the file using your favorite editor and add the image version details and save it.
143
146
1. Update your RHEL VM
144
147
```bash
145
148
sudo yum update
@@ -150,17 +153,17 @@ Use the following instructions to lock a RHEL 8.x VM to a particular minor relea
@@ -202,7 +205,7 @@ RHUI is available in all regions where RHEL on-demand images are available. It c
202
205
If you're using a network configuration to further restrict access from RHEL PAYG VMs, make sure the following IPs are allowed for `yum update` to work depending on the environment you're in:
203
206
204
207
205
-
```
208
+
```output
206
209
# Azure Global
207
210
RHUI 3
208
211
13.91.47.76
@@ -218,7 +221,7 @@ eastus - 52.142.4.99
218
221
australiaeast - 20.248.180.252
219
222
southeastasia - 20.24.186.80
220
223
221
-
# Azure US Government (To be deprecated after 10th April 2023. For RHUI 4 conections, use public RHUI IPs as provided above)
224
+
# Azure US Government (To be deprecated after 10th April 2023. For RHUI 4 connections, use public RHUI IPs as provided above)
222
225
13.72.186.193
223
226
13.72.14.155
224
227
52.244.249.194
@@ -235,7 +238,7 @@ southeastasia - 20.24.186.80
235
238
236
239
### Update expired RHUI client certificate on a VM
237
240
238
-
If you experience RHUI certificate issues from your Azure RHEL PAYG VM, reference the [troubleshooting guidance forRHUI certificate issuesin Azure](/troubleshoot/azure/virtual-machines/troubleshoot-linux-rhui-certificate-issues).
241
+
If you experience RHUI certificate issues from your Azure RHEL PAYG VM, reference the [Troubleshooting guidance forRHUI certificate issuesin Azure](/troubleshoot/azure/virtual-machines/troubleshoot-linux-rhui-certificate-issues).
239
242
240
243
241
244
@@ -263,12 +266,12 @@ This procedure is provided for reference only. RHEL PAYG images already have the
0 commit comments