Skip to content

Commit f1be8c0

Browse files
mburke5678mburke5678
authored
Merge pull request #86943 from mburke5678/mco-machineconfignode-output
OSDOCS13124 Add version information to the output oc get machineconfignodes/Add MCP column to MCN output
2 parents 203ed70 + dc1cbbe commit f1be8c0

File tree

3 files changed

+341
-65
lines changed

3 files changed

+341
-65
lines changed

‎machine_configuration/index.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@ include::modules/machine-config-drift-detection.adoc[leveloffset=+1]
4444

4545
include::modules/checking-mco-status.adoc[leveloffset=+1]
4646
include::modules/checking-mco-node-status.adoc[leveloffset=+1]
47+
include::modules/checking-mco-node-status-configuring.adoc[leveloffset=+2]
4748

4849
[role="_additional-resources"]
4950
.Additional resources

‎modules/checking-mco-node-status-configuring.adoc

Lines changed: 139 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,139 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * post_installation_configuration/machine-configuration-tasks.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="checking-mco-node-status-congifuring_{context}"]
7+
= Checking machine config node status
8+
9+
During the update of a machine config pool (MCP), you can monitor the progress of all control plane and worker nodes in your cluster by using the `oc get machineconfignodes` and `oc describe machineconfignodes` commands. These commands provide information that can be helpful if issues arise during the update and you need to troubleshoot a node.
10+
11+
You cannot use these commands with custom machine config pools.
12+
13+
For more information on the meaning of these fields, see "About checking machine config node status."
14+
15+
.Prerequisites
16+
17+
* You enabled the required Technology Preview features for your cluster by editing the `FeatureGate` CR named `cluster`:
18+
+
19+
[source,terminal]
20+
----
21+
$ oc edit featuregate cluster
22+
----
23+
+
24+
.Example `FeatureGate` CR
25+
[source,yaml]
26+
----
27+
apiVersion: config.openshift.io/v1
28+
kind: FeatureGate
29+
metadata:
30+
name: cluster
31+
spec:
32+
featureSet: TechPreviewNoUpgrade
33+
----
34+
+
35+
[WARNING]
36+
====
37+
Enabling the `TechPreviewNoUpgrade` feature set on your cluster cannot be undone and prevents minor version updates. This feature set allows you to enable these Technology Preview features on test clusters, where you can fully test them. Do not enable this feature set on production clusters.
38+
====
39+
+
40+
After you save the changes, new machine configs are created, the machine config pools are updated, and scheduling on each node is disabled while the change is being applied.
41+
42+
.Procedure
43+
44+
* View the update status of all nodes in the cluster, including the current and desired machine configurations, by running the following command:
45+
+
46+
[source,terminal]
47+
----
48+
$ oc get machineconfignodes
49+
----
50+
+
51+
.Example output
52+
[source,text]
53+
----
54+
NAME POOLNAME DESIREDCONFIG CURRENTCONFIG UPDATED
55+
ci-ln-mdb23yt-72292-kzdsg-master-0 master rendered-master-f21b093d20f68a7c06f922ed3ea5fbc8 rendered-master-1abc053eec29e6c945670f39d6dc8afa False
56+
ci-ln-mdb23yt-72292-kzdsg-master-1 master rendered-master-1abc053eec29e6c945670f39d6dc8afa rendered-master-1abc053eec29e6c945670f39d6dc8afa True
57+
ci-ln-mdb23yt-72292-kzdsg-master-2 master rendered-master-1abc053eec29e6c945670f39d6dc8afa rendered-master-1abc053eec29e6c945670f39d6dc8afa True
58+
ci-ln-mdb23yt-72292-kzdsg-worker-a-gfqjr worker rendered-worker-d0130cd74e9e576d7ba78ce166272bfb rendered-worker-8f61bf839898a4487c3b5263a430e94a False
59+
ci-ln-mdb23yt-72292-kzdsg-worker-b-gknq4 worker rendered-worker-8f61bf839898a4487c3b5263a430e94a rendered-worker-8f61bf839898a4487c3b5263a430e94a True
60+
ci-ln-mdb23yt-72292-kzdsg-worker-c-mffrx worker rendered-worker-8f61bf839898a4487c3b5263a430e94a rendered-worker-8f61bf839898a4487c3b5263a430e94a True
61+
----
62+
63+
* View of all machine config node status fields for the nodes in your cluster by running the following command:
64+
+
65+
[source,terminal]
66+
----
67+
$ oc get machineconfignodes -o wide
68+
----
69+
+
70+
.Example output
71+
[source,text]
72+
----
73+
NAME POOLNAME DESIREDCONFIG CURRENTCONFIG UPDATED UPDATEPREPARED UPDATEEXECUTED UPDATEPOSTACTIONCOMPLETE UPDATECOMPLETE RESUMED UPDATECOMPATIBLE UPDATEDFILESANDOS CORDONEDNODE DRAINEDNODE REBOOTEDNODE RELOADEDCRIO UNCORDONEDNODE
74+
ci-ln-g6dr34b-72292-g9btv-master-0 master rendered-master-d4e122320b351cdbe1df59ddb63ddcfc rendered-master-6f2064fcb36d2a914de5b0c660dc49ff False True Unknown False False False True Unknown False False False False False
75+
ci-ln-g6dr34b-72292-g9btv-master-1 master rendered-master-6f2064fcb36d2a914de5b0c660dc49ff rendered-master-6f2064fcb36d2a914de5b0c660dc49ff True False False False False False False False False False False False False
76+
ci-ln-g6dr34b-72292-g9btv-master-2 master rendered-master-6f2064fcb36d2a914de5b0c660dc49ff rendered-master-6f2064fcb36d2a914de5b0c660dc49ff True False False False False False False False False False False False False
77+
ci-ln-g6dr34b-72292-g9btv-worker-a-sjh5r worker rendered-worker-671b88c8c569fa3f60dc1a27cf9c91f2 rendered-worker-d5534cb730e5e108905fc285c2a42b6c False True Unknown False False False True Unknown False False False False False
78+
ci-ln-g6dr34b-72292-g9btv-worker-b-xthbz worker rendered-worker-d5534cb730e5e108905fc285c2a42b6c rendered-worker-d5534cb730e5e108905fc285c2a42b6c True False False False False False False False False False False False False
79+
ci-ln-g6dr34b-72292-g9btv-worker-c-gnpd6 worker rendered-worker-d5534cb730e5e108905fc285c2a42b6c rendered-worker-d5534cb730e5e108905fc285c2a42b6c True False False False False False False False False False False False False
80+
----
81+
82+
* Check the update status of nodes in a specific machine config pool by running the following command:
83+
+
84+
[source,terminal]
85+
----
86+
$ oc get machineconfignodes $(oc get machineconfignodes -o json | jq -r '.items[]|select(.spec.pool.name=="<pool_name>")|.metadata.name') <1>
87+
----
88+
+
89+
.Example output
90+
[source,text]
91+
----
92+
NAME POOLNAME DESIREDCONFIG CURRENTCONFIG UPDATED
93+
ci-ln-g6dr34b-72292-g9btv-worker-a-sjh5r worker rendered-worker-d5534cb730e5e108905fc285c2a42b6c rendered-worker-d5534cb730e5e108905fc285c2a42b6c True
94+
ci-ln-g6dr34b-72292-g9btv-worker-b-xthbz worker rendered-worker-d5534cb730e5e108905fc285c2a42b6c rendered-worker-faf6b50218a8bbce21f1370866283de5 False
95+
ci-ln-g6dr34b-72292-g9btv-worker-c-gnpd6 worker rendered-worker-faf6b50218a8bbce21f1370866283de5 rendered-worker-faf6b50218a8bbce21f1370866283de5 True
96+
----
97+
98+
* Check the update status of an individual node by running the following command:
99+
+
100+
[source,terminal]
101+
----
102+
$ oc describe machineconfignode/<node_name>
103+
----
104+
+
105+
.Example output
106+
[source,text]
107+
----
108+
Name: <node_name>
109+
Namespace:
110+
Labels: <none>
111+
Annotations: <none>
112+
API Version: machineconfiguration.openshift.io/v1alpha1
113+
Kind: MachineConfigNode
114+
Metadata:
115+
Creation Timestamp: 2023-10-17T13:08:58Z
116+
Generation: 1
117+
Resource Version: 49443
118+
UID: 4bd758ab-2187-413c-ac42-882e61761b1d
119+
Spec:
120+
Node Ref:
121+
Name: <node_name>
122+
Pool:
123+
Name: master
124+
ConfigVersion:
125+
Desired: rendered-worker-823ff8dc2b33bf444709ed7cd2b9855b
126+
Status:
127+
# ...
128+
Message: Drained node. The drain is complete as the desired drainer matches current drainer: drain-rendered-worker-01f27f752eb84eba917450e43636b210
129+
Reason: UpdateExecutedDrained
130+
Status: True
131+
Type: Drained
132+
Last Transition Time: 2025-01-14T15:45:55Z
133+
# ...
134+
Config Version:
135+
Current: rendered-master-8110974a5cea69dff5b263237b58abd8
136+
Desired: rendered-worker-823ff8dc2b33bf444709ed7cd2b9855b
137+
Observed Generation: 6
138+
# ...
139+
----

0 commit comments

Comments
 (0)