Created
March 1, 2017 13:11
-
-
Save garethahealy/8ca8ba8eb943f433448bf35b30d746d9 to your computer and use it in GitHub Desktop.
oc adm diagnostics
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [root@exvoseqam1:/home/gahealy]# oc adm diagnostics --diaglevel=3 | |
| ERROR: [DNet2008 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/run_pod.go:141] | |
| [Logs for network diagnostic pod on node "exvoseqam1.metoffice.gov.uk" failed: container "network-diag-pod-0b1pq" in pod "network-diag-pod-0b1pq" is not available, See the errors below in the output from the network diagnostic pod on node "exvoseqan2.metoffice.gov.uk": | |
| [Note] Running diagnostic: CheckExternalNetwork | |
| Description: Check that external network is accessible within a pod | |
| [Note] Running diagnostic: CheckNodeNetwork | |
| Description: Check that pods in the cluster can access its own node. | |
| [Note] Running diagnostic: CheckPodNetwork | |
| Description: Check pod to pod communication in the cluster. In case of ovs-subnet network plugin, all pods should be able to communicate with each other and in case of multitenant network plugin, pods in non-global projects should be isolated and pods in global projects should be able to access any pod in the cluster and vice versa. | |
| [Note] Running diagnostic: CheckServiceNetwork | |
| Description: Check pod to service communication in the cluster. In case of ovs-subnet network plugin, all pods should be able to communicate with all services and in case of multitenant network plugin, services in non-global projects should be isolated and pods in global projects should be able to access any service in the cluster. | |
| ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/diagnostics/networkpod/service.go:187] | |
| Connectivity from pod "network-diag-global-ns-37fuf/network-diag-test-pod-dftp0" to service "network-diag-global-ns-37fuf/network-diag-test-service-2lc3v" failed. Error: exit status 124, Out: | |
| [Note] Running diagnostic: CollectNetworkInfo | |
| Description: Collect network information in the cluster. | |
| [Note] Summary of diagnostics execution (version v3.4.1.5): | |
| [Note] Errors seen: 1 | |
| , Logs for network diagnostic pod on node "exvoseqam2.metoffice.gov.uk" failed: container "network-diag-pod-djhpg" in pod "network-diag-pod-djhpg" is not available, Logs for network diagnostic pod on node "exvoseqam3.metoffice.gov.uk" failed: container "network-diag-pod-nosbc" in pod "network-diag-pod-nosbc" is not available, See the errors below in the output from the network diagnostic pod on node "exvoseqan1.metoffice.gov.uk": | |
| [Note] Running diagnostic: CheckExternalNetwork | |
| Description: Check that external network is accessible within a pod | |
| [Note] Running diagnostic: CheckNodeNetwork | |
| Description: Check that pods in the cluster can access its own node. | |
| [Note] Running diagnostic: CheckPodNetwork | |
| Description: Check pod to pod communication in the cluster. In case of ovs-subnet network plugin, all pods should be able to communicate with each other and in case of multitenant network plugin, pods in non-global projects should be isolated and pods in global projects should be able to access any pod in the cluster and vice versa. | |
| [Note] Running diagnostic: CheckServiceNetwork | |
| Description: Check pod to service communication in the cluster. In case of ovs-subnet network plugin, all pods should be able to communicate with all services and in case of multitenant network plugin, services in non-global projects should be isolated and pods in global projects should be able to access any service in the cluster. | |
| ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/diagnostics/networkpod/service.go:187] | |
| Connectivity from pod "network-diag-global-ns-37fuf/network-diag-test-pod-c7k8g" to service "network-diag-global-ns-37fuf/network-diag-test-service-2lc3v" failed. Error: exit status 124, Out: | |
| [Note] Running diagnostic: CollectNetworkInfo | |
| Description: Collect network information in the cluster. | |
| [Note] Summary of diagnostics execution (version v3.4.1.5): | |
| [Note] Errors seen: 1 | |
| , Logs for network diagnostic pod on node "exvoseqain3.metoffice.gov.uk" failed: container "network-diag-pod-xozpy" in pod "network-diag-pod-xozpy" is not available, Logs for network diagnostic pod on node "exvoseqain1.metoffice.gov.uk" failed: container "network-diag-pod-ypztk" in pod "network-diag-pod-ypztk" is not available, Logs for network diagnostic pod on node "exvoseqain2.metoffice.gov.uk" failed: container "network-diag-pod-zpmxk" in pod "network-diag-pod-zpmxk" is not available] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment