From 5d5ecab58c154429fdd318b0de91016d607585ab Mon Sep 17 00:00:00 2001 From: Mark McLoughlin Date: Wed, 13 Feb 2019 15:06:31 +0000 Subject: [PATCH] docs/troubleshooting: update machines namespace commit 56b34f926 changed the namespace from openshift-cluster-api to openshift-machine-api. Update the troubleshooting doc also. --- docs/user/troubleshooting.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index ad6bbc91061..373cb833a92 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -13,7 +13,7 @@ The installer doesn't provision worker nodes directly, like it does with master The status of the Machine API Operator can be checked by running the following command from the machine used to install the cluster: ```sh -oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-cluster-api get deployments +oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-machine-api get deployments ``` If the API is unavailable, that will need to be [investigated first](#kubernetes-api-is-unavailable). @@ -30,7 +30,7 @@ machine-api-operator 1 1 1 1 1d Check the machine controller logs with the following command. ```sh -oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-cluster-api logs deployments/clusterapi-manager-controllers --container=machine-controller +oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-machine-api logs deployments/clusterapi-manager-controllers --container=machine-controller ``` ### Kubernetes API is Unavailable @@ -107,7 +107,7 @@ This is the generic version of the [*No Worker Nodes Created*](#no-worker-nodes- $ oc --config=${INSTALL_DIR}/auth/kubeconfig get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system etcd-member-wking-master-0 1/1 Running 0 46s -openshift-cluster-api machine-api-operator-586bd5b6b9-bxq9s 0/1 Pending 0 1m +openshift-machine-api machine-api-operator-586bd5b6b9-bxq9s 0/1 Pending 0 1m openshift-cluster-dns-operator cluster-dns-operator-7f4f6866b9-kzth5 0/1 Pending 0 2m ... ``` @@ -115,7 +115,7 @@ openshift-cluster-dns-operator cluster-dns-operator-7f4f6866b9-kzth5 You can investigate any pods listed as `Pending` with: ```sh -oc --config=${INSTALL_DIR}/auth/kubeconfig describe -n openshift-cluster-api pod/machine-api-operator-586bd5b6b9-bxq9s +oc --config=${INSTALL_DIR}/auth/kubeconfig describe -n openshift-machine-api pod/machine-api-operator-586bd5b6b9-bxq9s ``` which may show events with warnings like: @@ -127,7 +127,7 @@ Warning FailedScheduling 1m (x10 over 1m) default-scheduler 0/1 nodes are av You can get the image used for a crashing pod with: ```console -$ oc --config=${INSTALL_DIR}/auth/kubeconfig get pod -o "jsonpath={range .status.containerStatuses[*]}{.name}{'\t'}{.state}{'\t'}{.image}{'\n'}{end}" -n openshift-cluster-api machine-api-operator-586bd5b6b9-bxq9s +$ oc --config=${INSTALL_DIR}/auth/kubeconfig get pod -o "jsonpath={range .status.containerStatuses[*]}{.name}{'\t'}{.state}{'\t'}{.image}{'\n'}{end}" -n openshift-machine-api machine-api-operator-586bd5b6b9-bxq9s machine-api-operator map[running:map[startedAt:2018-11-13T19:04:50Z]] registry.svc.ci.openshift.org/openshift/origin-v4.0-20181113175638@sha256:c97d0b53b98d07053090f3c9563cfd8277587ce94f8c2400b33e246aa08332c7 ```