openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Merge pull request #90851 from xenolinux/419-replace-bullets

Browse Source 
[enterprise-4.19] No#jira: Replace bullets with numbered steps
This commit is contained in:
Servesha Dudhgaonkar
2025-03-21 11:43:32 +05:30
committed by GitHub
parent b013ecd855 72a92aef40
commit bbbbdfefac
1 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
modules/hcp-ts-nodes-stuck.adoc
View File

@@ -1,26 +1,24 @@
// Module included in the following assemblies:
//
// * hosted_control_planes/hcp-troubleshooting.adoc
:_mod-docs-content-type: PROCEDURE
[id="hcp-ts-nodes-stuck_{context}"]
= Worker nodes are stuck in the NotReady state
During cluster creation, nodes enter the `NotReady` state temporarily while the networking stack is rolled out. This part of the process is normal. However, if this part of the process takes longer than 15 minutes, an issue might have occurred.
During cluster creation, nodes enter the `NotReady` state temporarily while the networking stack is rolled out. This part of the process is normal. However, if this part of the process takes longer than 15 minutes, identify the problem by investigating the node object and pods.
.Procedure
Identify the problem by investigating the node object and pods:
* Enter the following command to view the conditions on the node object and determine why the node is not ready:
. Enter the following command to view the conditions on the node object and determine why the node is not ready:
+
[source,terminal]
----
$ oc get nodes -o yaml
----
* Enter the following command to look for failing pods within the cluster:
. Enter the following command to look for failing pods within the cluster:
+
[source,terminal]
----
$ oc get pods -A --field-selector=status.phase!=Running,status,phase!=Succeeded
----
----