Skip to content

Simplify worker node troubleshooting steps #1050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
openshift-merge-robot merged 1 commit into from
Jan 14, 2019
Merged

Simplify worker node troubleshooting steps #1050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions docs/user/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,23 +11,24 @@ 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 pods
oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-cluster-api get deployments
```

If the API is unavailable, that will need to be [investigated first](#kubernetes-api-is-unavailable).

The previous command should yield output similar to the following:

```
NAME READY STATUS RESTARTS AGE
clusterapi-manager-controllers-774dc4557-nx5xq 3/3 Running 0 4h
machine-api-operator-7894d8f85-lq2ts 1/1 Running 0 4h
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
cluster-autoscaler-operator 1 1 1 1 1d
clusterapi-manager-controllers 1 1 1 1 1d
machine-api-operator 1 1 1 1 1d
```

The logs for the machine-controller container within the `clusterapi-manager-controllers` pod need to be checked to determine why the workers haven't been created. That can be done with the following (the exact name of the pod will need to be substituted):
Check the machine controller logs with the following command.

```sh
oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-cluster-api logs clusterapi-manager-controllers-774dc4557-nx5xq --container=machine-controller
oc --config=${INSTALL_DIR}/auth/kubeconfig --namespace=openshift-cluster-api logs deployments/clusterapi-manager-controllers --container=machine-controller
```

### Kubernetes API is Unavailable
Expand Down