Skip to content

Commit 6fcd985

Browse files
authored
Merge pull request #90229 from ShaunaDiaz/OSDOCS-13300
OSDOCS-13300: adds RHEL updates to MicroShift
2 parents c56357b + d7c89c1 commit 6fcd985

File tree

4 files changed

+27
-21
lines changed

4 files changed

+27
-21
lines changed

microshift_updating/microshift-update-options.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,9 @@ To begin a {microshift-short} update by embedding in a {op-system-ostree} image,
4848

4949
* xref:../microshift_updating/microshift-update-rpms-ostree.adoc#microshift-update-rpms-ostree[Applying updates on an OSTree system]
5050

51-
To understand more about Greenboot, see the following documentation:
51+
To understand more about greenboot, see the following documentation:
5252

53-
* xref:../microshift_install_get_ready/microshift-greenboot.adoc#microshift-greenboot[The Greenboot health check]
53+
* xref:../microshift_install_get_ready/microshift-greenboot.adoc#microshift-greenboot[The greenboot health check]
5454
* xref:../microshift_running_apps/microshift-greenboot-workload-scripts.adoc#microshift-greenboot-workload-scripts[Greenboot workload health check scripts]
5555

5656
[id="microshift-update-options-manual-rpm-updates_{context}"]
@@ -72,7 +72,7 @@ You can update {op-system-ostree} or {op-system-base} without updating {microshi
7272
//additional resources for updating RHEL alone
7373
[role="_additional-resources"]
7474
.Additional resources
75-
* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/index[Managing RHEL for Edge images]
75+
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/index[Composing, installing, and managing RHEL for Edge images]
7676

7777
[id="microshift-update-options-simultaneous-microshift-rhel-updates_{context}"]
7878
== Simultaneous {microshift-short} and operating system updates
@@ -87,8 +87,8 @@ You can update {op-system-ostree} or {op-system-base} and update {microshift-sho
8787
[role="_additional-resources"]
8888
.Additional resources
8989
* link:https://access.redhat.com/articles/rhel-eus#c5[How to Access EUS]
90-
* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/composing_a_customized_rhel_system_image/index[Composing a customized RHEL system image]
90+
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/composing_a_customized_rhel_system_image/index[Composing a customized RHEL system image]
9191
* xref:../microshift_updating/microshift-update-rpms-ostree.adoc#microshift-update-rpms-ostree[Applying updates on an OSTree system]
9292
* xref:../microshift_updating/microshift-update-rpms-manually.adoc#microshift-update-rpms-manually[Applying updates manually with RPMs]
93-
* xref:../microshift_install_get_ready/microshift-greenboot.adoc#microshift-greenboot[The Greenboot system health check]
93+
* xref:../microshift_install_get_ready/microshift-greenboot.adoc#microshift-greenboot[The greenboot system health check]
9494
* xref:../microshift_running_apps/microshift-greenboot-workload-scripts.adoc#microshift-greenboot-workload-scripts[Greenboot workload scripts]

modules/microshift-updates-rhde-config-rhel-repos.adoc

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -18,39 +18,40 @@ When using RPM updates, avoid creating an unsupported configuration or breaking
1818

1919
. Avoid unintended updates by locking your operating system version by running the following command:
2020
+
21-
[source,terminal]
21+
[source,terminal,subs="+quotes"]
2222
----
23-
$ sudo subscription-manager release --set=<x.y> # <1>
23+
$ sudo subscription-manager release --set=_<x.y>_ # <1>
2424
----
25-
<1> Replace _<x.y>_ with the major and minor version of your compatible {op-system-base} system. For example, _9.4_.
25+
<1> Replace _<x.y>_ with the major and minor version of your compatible {op-system-base} system. For example, _9.6_.
2626

27+
//this is the same command as above; is this correct?
2728
. Update both {microshift-short} and {op-system-base} versions by running the following command:
2829
+
2930
[source,terminal]
3031
----
31-
$ sudo subscription-manager release --set=<9.4> command. # <1>
32+
$ sudo subscription-manager release --set={ocp-version} # <1>
3233
----
33-
<1> Replace _<9.4>_ with the major and minor version of your compatible {op-system-base} system.
34+
<1> You can replace _{ocp-version}_ with the major and minor version of your compatible {op-system-base} system if it is not the same version given in this example.
3435

3536
. If you are using an EUS {microshift-short} release, disable the {op-system-base} standard-support-scope repositories by running the following command:
3637
+
3738
[source,terminal]
3839
----
3940
$ sudo subscription-manager repos \
40-
--disable=rhel-<9>-for-x86_64-appstream-rpms \ # <1>
41-
--disable=rhel-<9>-for-x86_64-baseos-rpms
41+
--disable=rhel-{op-system-version-major}-for-$(uname -m)-appstream-rpms \ # <1>
42+
--disable=rhel-{op-system-version-major}-for-$(uname -m)-baseos-rpms
4243
----
43-
<1> Replace _<9>_ with the major version of your compatible {op-system-base} system.
44+
<1> You can replace _{op-system-version-major}_ with the major version of your compatible {op-system-base} system if it is not same version given in this example.
4445

4546
. After you disable the standard-support repositories, enable the {op-system-base} EUS repos by running the following command:
4647
+
4748
[source,terminal]
4849
----
4950
$ sudo subscription-manager repos \
50-
--enable rhel-<9>-for-x86_64-appstream-eus-rpms \ # <1>
51-
--enable rhel-<9>-for-x86_64-baseos-eus-rpms`
51+
--enable rhel-{op-system-version-major}-for-$(uname -m)-appstream-eus-rpms \ # <1>
52+
--enable rhel-{op-system-version-major}-for-$(uname -m)-baseos-eus-rpms
5253
----
53-
<1> Replace _<9>_ with the major version of your compatible {op-system-base} system.
54+
<1> You can replace _{op-system-version-major}_ with the major version of your compatible {op-system-base} system if it is not same version given in this example.
5455

5556
.Verification
5657

modules/microshift-updating-rpms-ostree.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,11 @@ $ sudo composer-cli sources add {rpm-repo-version}.toml
5454

5555
. Build a new image of {op-system-ostree} that contains the new version of {microshift-short}. To determine the steps required, use the following documentation:
5656

57-
* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/managing-rhel-for-edge-images_composing-installing-managing-rhel-for-edge-images#proc_building-a-commit-update_managing-rhel-for-edge-images[Building a RHEL for Edge commit update]
57+
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/managing-rhel-for-edge-images_composing-installing-managing-rhel-for-edge-images#proc_building-a-commit-update_managing-rhel-for-edge-images[Building a commit update]
5858
5959
. Update the host to use the new image of {op-system-ostree}. To determine the steps required, use the following documentation:
6060

61-
* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/managing-rhel-for-edge-images_composing-installing-managing-rhel-for-edge-images#how-are-rhel-for-edge-image-updates-deployed_managing-rhel-for-edge-images[Deploying RHEL for Edge image updates]
61+
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/managing-rhel-for-edge-images_composing-installing-managing-rhel-for-edge-images#how-are-rhel-for-edge-image-updates-deployed_managing-rhel-for-edge-images[How RHEL for Edge image updates are deployed]
6262
6363
. Reboot the host to apply updates by running the following command:
6464
+

modules/microshift-updating-rpms-z.adoc

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,10 @@
88

99
Updating {microshift-short} on non `rpm-ostree` systems such as {op-system-base-full} requires downloading then updating the RPMs. For example, use the following procedure to upgrade from 4.19.1 to 4.19.2.
1010

11+
include::snippets/microshift-unsupported-config-warn.adoc[leveloffset=+1]
12+
1113
.Prerequisites
14+
1215
* The system requirements for installing {microshift-short} have been met.
1316
* You have root user access to the host.
1417
* The version of {microshift-short} you have is compatible to upgrade to the version you are preparing to use.
@@ -21,13 +24,15 @@ You cannot downgrade {microshift-short} with this process. Downgrades are not su
2124
====
2225

2326
.Procedure
24-
* Update the {microshift-short} RPMs by running the following command:
27+
28+
. Update the {microshift-short} RPMs by running the following command:
2529
+
2630
[source,terminal]
2731
----
2832
$ sudo dnf update microshift
2933
----
30-
* Restart {microshift-short} by running the following command:
34+
35+
. Restart {microshift-short} by running the following command:
3136
+
3237
[source,terminal]
3338
----
@@ -36,5 +41,5 @@ $ sudo systemctl restart microshift
3641

3742
[NOTE]
3843
====
39-
The system health check runs on this update type, but does not perform any actions. If the update fails, an error message appears with the instruction to check the logs.
44+
The greenboot system health check runs on this update type, but does not perform any actions. If the update fails, an error message appears with the instruction to check the logs.
4045
====

0 commit comments

Comments
 (0)