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: modules/gathering-log-data.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,4 +6,4 @@
6
6
[id="gathering-log-data_{context}"]
7
7
= Gathering log data for a support case
8
8
9
-
To gather data from your cluster, including log data, use the `oc adm must-gather` command. See _Gathering data about your cluster for Red Hat Support_.
9
+
To gather data from your cluster, including log data, use the `oc adm must-gather` command. See _Gathering data about your cluster_.
* If there are no available updates, updates that are supported but not recommended might still be available.
54
70
See _Updating along a conditional update path_ for more information.
55
-
71
+
ifndef::openshift-origin[]
56
72
* For details and information on how to perform an `EUS-to-EUS` channel update, please refer to the _Preparing to perform an EUS-to-EUS upgrade_ page, listed in the Additional resources section.
73
+
endif::openshift-origin[]
57
74
====
58
-
75
+
ifndef::openshift-origin[]
59
76
. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
77
+
// In OKD, no need to set the channel.
60
78
//this example will need to be updated per eus release to reflect options available
61
-
62
79
+
63
80
[source,terminal]
64
81
----
@@ -86,6 +103,7 @@ Update recommendations can change over time, as they are based on what update op
86
103
87
104
If you cannot see an update path to your target minor version, keep updating your cluster to the latest patch release for your current version until the next minor version is available in the path.
When reaching out to Red Hat support for issues with an update, it is important to provide data for the support team to use for troubleshooting your failed cluster update.
11
+
endif::openshift-origin[]
12
+
ifdef::openshift-origin[]
13
+
If your cluster update fails, you can examine cluster data to troubleshoot the failure.
* xref:../../updating/updating_a_cluster/eus-eus-update.adoc#eus-eus-update[Performing an EUS-to-EUS update]
64
+
endif::openshift-origin[]
63
65
* xref:../../updating/updating_a_cluster/updating-cluster-cli.adoc#update-conditional-upgrade-pathupdating-cluster-cli[Updating along a conditional update path]
66
+
ifndef::openshift-origin[]
64
67
* xref:../../updating/understanding_updates/understanding-update-channels-release.adoc#understanding-update-channels-releases[Understanding update channels and releases]
0 commit comments