Mirror host ping check fails

Bug #1694501 reported by Clark Boylan
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We have jobs that fail the mirror host ping check. This is run early in the job to fail quickly if we don't expect the host networking to otherwise function and fail in obtuse ways. However, we aren't currently tracking when this occurs. Add this bug to track it with e-r.

Example from http://logs.openstack.org/10/466910/1/gate/gate-grenade-dsvm-neutron-ubuntu-xenial/6be4506/logs/devstack-gate-setup-host.txt.gz

2017-05-23 21:50:20.418 | localhost | SUCCESS | network_sanity_check : Get NODEPOOL_MIRROR_HOST >>
2017-05-23 21:50:20.627 | localhost | SUCCESS | network_sanity_check : Get NODEPOOL_PYPI_MIRROR >>
2017-05-23 21:50:30.888 | localhost | FAILED | network_sanity_check : Perform ping check | rc=1 >>
PING mirror.la1.citycloud.openstack.org ( 56(84) bytes of data.

--- mirror.la1.citycloud.openstack.org ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
 to retry, use: --limit @/home/jenkins/workspace/gate-grenade-dsvm-neutron-ubuntu-xenial/devstack-gate/playbooks/setup_host.retry

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.