No route to host after deployment
Closed this issue · 6 comments
jci commented
Description
Provide a brief description of your issue here.
After deployment, running "oc new-project something" and "oc new-app httpd" (or any other image in the registry) I got the following:
1s 1s 1 httpd-1-kdlqs.15b674228722f6da Pod spec.containers{httpd} Warning Failed kubelet, q-openshift-ncompute-02.cluster.local Failed to pull image "docker-registry.default.svc:5000/openshift/httpd@sha256:109a5ab8afbbdff4a65167349d3af4548f8e4ad93e56bb9350670764a49418a9": rpc error: code = Unknown desc = Get http://docker-registry.default.svc:5000/v2/: dial tcp 192.168.157.173:5000: connect: no route to host
192.168.157.173 matches with the definition of openshift_portal_net.
Version
Please put the following version information in the code block
indicated below.
- Ansible 2.7.10
- using openshift-ansible for 3.11 release as June 2019.
Steps To Reproduce
- Deploy cluster
- Create new project
Project fails
Expected Results
Project should work and image should be pulled correctly.
Observed Results
This is a disconnected installation (no internet due to requirements). All images were pushed to a local registry that docker picks up correctly.
Network segment is 172.30.0.0 for eth0 and cannot be changed.
Additional Information
- RHEL 7.6
- Inventory:
q-openshift-nmaster-02.cluster.local ansible_host=172.30.145.52
q-openshift-nmaster-04.cluster.local ansible_host=172.30.145.53
q-openshift-nmaster-06.cluster.local ansible_host=172.30.145.54
q-openshift-ninfra-02.cluster.local ansible_host=172.30.145.55
q-openshift-ninfra-04.cluster.local ansible_host=172.30.145.56
q-openshift-ninfra-06.cluster.local ansible_host=172.30.145.57
q-openshift-ncompute-02.cluster.local ansible_host=172.30.145.58
[masters]
q-openshift-nmaster-02.cluster.local
q-openshift-nmaster-04.cluster.local
q-openshift-nmaster-06.cluster.local
[etcd]
q-openshift-nmaster-04.cluster.local
q-openshift-nmaster-04.cluster.local
q-openshift-nmaster-06.cluster.local
[nodes]
q-openshift-nmaster-02.cluster.local openshift_node_group_name="node-config-master"
q-openshift-nmaster-04.cluster.local openshift_node_group_name="node-config-master"
q-openshift-nmaster-06.cluster.local openshift_node_group_name="node-config-infra"
q-openshift-ninfra-02.cluster.local openshift_node_group_name="node-config-infra"
q-openshift-ninfra-04.cluster.local openshift_node_group_name="node-config-compute"
q-openshift-ninfra-06.cluster.local openshift_node_group_name="node-config-compute"
q-openshift-ncompute-02.cluster.local openshift_node_group_name="node-config-compute"
[nfs]
q-openshift-nmaster-02.cluster.local
[OSEv3:vars]
ansible_user=root
openshift_clock_enabled=True
openshift_use_system_containers=false
openshift_disable_check=memory_availability,disk_availability,docker_storage,docker_image_availability
openshift_deployment_type=openshift-enterprise
openshift_release="3.11.88"
debug_level=2
openshift_install_examples=True
openshift_master_default_subdomain=apps.openshift.qa.cluster.local
openshift_master_cluster_method=native
openshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'True', 'challenge': 'True', 'kind': 'HTPasswdPasswordIdentityProvider'}]
openshift_master_htpasswd_users={'admin': 'XXXXXXXhashedXXXXXXXXXXXXX'}
openshift_enable_service_catalog=false
template_service_broker_install=false
ansible_service_broker_install=false
openshift_service_catalog_remove=True
ansible_service_broker_remove=True
template_service_broker_remove=True
openshift_metrics_install_metrics=True
openshift_metrics_server_install=True
openshift_cluster_monitoring_operator_install=false
openshift_cluster_monitoring_operator_prometheus_storage_capacity="50Gi"
openshift_cluster_monitoring_operator_alertmanager_storage_capacity="2Gi"
openshift_web_console_install=True
openshift_console_install=True
openshift_enable_olm=True
openshift_storage_glusterfs_namespace=app-storage
openshift_storage_glusterfs_storageclass=True
openshift_storage_glusterfs_storageclass_default=false
openshift_storage_glusterfs_block_deploy=True
openshift_storage_glusterfs_block_host_vol_size=100
openshift_storage_glusterfs_block_storageclass=True
openshift_storage_glusterfs_block_storageclass_default=false
oreg_url=external-registry.cloud/ose-${component}:${version}
openshift_examples_modify_imagestreams=True
osm_etcd_image=external-registry.cloud/rhel7/etcd:3.2.22
openshift_docker_options='--selinux-enabled --insecure-registry=external-registry.cloud'
openshift_docker_hosted_registry_insecure=True
openshift_additional_ca=/etc/docker/certs.d/external-registry.cloud/ca.crt
openshift_redeploy_openshift_ca=True
openshift_master_overwrite_named_certificates=True
os_firewall_use_firewalld=True
openshift_use_openvswitch_system_container=False
openshift_portal_net=192.168.0.0/16
- external-registry.cloud is a machine with an exposed registry. Docker pulls the images correctly.
- changing the network segment for openshift_portal_net is allowed but only if it does not clash with the eth0 network segment (which is 172.30.0.0/16 already)
- several iterations of osm_cluster_network_cidr and openshift_portal_net in different segments have the same result
vrutkovs commented
jci commented
We managed to run the network diagnostics images.
Running oc adm diagnostics NetworkCheck gives the following:
[Note] Determining if client configuration exists for client/cluster diagnostics
Info: Successfully read a client config file at '/root/.kube/config'
Info: Using context for cluster-admin access: 'default/q-openshift-master-02-cluster-local:8443/system:admin'
[Note] Running diagnostic: NetworkCheck
Description: Create a pod on all schedulable nodes and run network diagnostics from the application standpoint
ERROR: [DNet2008 from diagnostic NetworkCheck@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/run_pod.go:231]
[See the errors below in the output from the network diagnostic pod on node "q-openshift-ninfra-06.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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.
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-8vs64" to pod "network-diag-ns-7fr98/network-diag-test-pod-7l4dj" failed. Error: exit status 1, Out: PING 10.88.0.98 (10.88.0.98) 56(84) bytes of data.
--- 10.88.0.98 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-8vs64" to service "default/docker-registry" failed. Error: exit status 1, Out: bash: connect: Connection refused
bash: /dev/tcp/10.199.73.132/5000: Connection refused
ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-8vs64" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 3
, See the errors below in the output from the network diagnostic pod on node "q-openshift-master-06.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-bqqfl" to service "default/docker-registry" failed. Error: exit status 1, Out: bash: connect: Connection refused
bash: /dev/tcp/10.199.73.132/5000: Connection refused
ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-bqqfl" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 2
, See the errors below in the output from the network diagnostic pod on node "q-openshift-ninfra-02.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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.
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-6xhwk" to pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" failed. Error: exit status 1, Out: PING 10.88.0.57 (10.88.0.57) 56(84) bytes of data.
--- 10.88.0.57 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-6xhwk" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 2
, See the errors below in the output from the network diagnostic pod on node "q-openshift-master-02.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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.
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" to pod "network-diag-ns-2lwnj/network-diag-test-pod-6xhwk" failed. Error: exit status 1, Out: PING 10.88.0.67 (10.88.0.67) 56(84) bytes of data.
--- 10.88.0.67 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" to pod "network-diag-ns-7fr98/network-diag-test-pod-4pgpc" failed. Error: exit status 1, Out: PING 10.88.0.73 (10.88.0.73) 56(84) bytes of data.
--- 10.88.0.73 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" to service "default/docker-registry" failed. Error: exit status 1, Out: bash: connect: Connection refused
bash: /dev/tcp/10.199.73.132/5000: Connection refused
ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 4
, See the errors below in the output from the network diagnostic pod on node "q-openshift-ntrabajo-02.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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.
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-lpc8k" to pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" failed. Error: exit status 1, Out: PING 10.88.0.57 (10.88.0.57) 56(84) bytes of data.
--- 10.88.0.57 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-lpc8k" to pod "network-diag-ns-7fr98/network-diag-test-pod-4pgpc" failed. Error: exit status 1, Out: PING 10.88.0.73 (10.88.0.73) 56(84) bytes of data.
--- 10.88.0.73 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-lpc8k" to service "default/docker-registry" failed. Error: exit status 124, Out:
ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-lpc8k" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 4
, See the errors below in the output from the network diagnostic pod on node "q-openshift-master-04.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-bvhzl" to service "default/docker-registry" failed. Error: exit status 1, Out: bash: connect: Connection refused
bash: /dev/tcp/10.199.73.132/5000: Connection refused
ERROR: [DSvcNet1010 from diagnostic CheckServiceNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-bvhzl" to service "network-diag-ns-2lwnj/network-diag-test-service-4zx7z" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 2
, See the errors below in the output from the network diagnostic pod on node "q-openshift-ninfra-04.cluster.local":
[Note] Running diagnostic: CheckExternalNetwork
Description: Check that external network is accessible within a pod
WARN: [DExtNet1001 from diagnostic CheckExternalNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/external.go:46]
Pinging external address "www.redhat.com" failed. Check if the admin intentionally blocked access to the external network. Error: exit status 1
[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.
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-p2vnh" to pod "network-diag-ns-2lwnj/network-diag-test-pod-4m4t7" failed. Error: exit status 1, Out: PING 10.88.0.57 (10.88.0.57) 56(84) bytes of data.
--- 10.88.0.57 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
ERROR: [DPodNet1008 from diagnostic CheckPodNetwork@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/pod.go:186]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-p2vnh" to pod "network-diag-ns-7fr98/network-diag-test-pod-4pgpc" failed. Error: exit status 1, Out: PING 10.88.0.73 (10.88.0.73) 56(84) bytes of data.
--- 10.88.0.73 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
[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/oc/cli/admin/diagnostics/diagnostics/cluster/network/in_pod/service.go:193]
Connectivity from pod "network-diag-ns-2lwnj/network-diag-test-pod-p2vnh" to service "default/docker-registry" failed. Error: exit status 124, Out:
[Note] Running diagnostic: CollectNetworkInfo
Description: Collect network information in the cluster.
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Warnings seen: 1
[Note] Errors seen: 3
]
Info: Additional info collected under "/tmp/openshift" for further analysis
[Note] Summary of diagnostics execution (version v3.11.88):
[Note] Errors seen: 1
As mentioned, external access is not possible, so the ping error to www.redhat.com will fail. But then tries to connect to registry and fails, and so on.
openshift-bot commented
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
openshift-bot commented
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-bot commented
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
openshift-ci-robot commented
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.