Nightly 6.7 - 5-22-NFS-Volume - 2018-03-28 - Cannot connect to docker daemon

[rajanashok]

Running command 'docker -H 10.192.247.107:2376 --tls volume create --opt VolumeStore=nfsVolumeStore 2>&1'.	
07:36:00.841	INFO	${rc} = 1	
07:36:00.841	INFO	${volumeOutput} = Cannot connect to the Docker daemon at tcp://10.192.247.107:2376. Is the docker daemon running?

Detailed test log is missing for this nightly test, needs investigation for the root cause.
https://storage.cloud.google.com/vic-ci-logs/vic_nightly_logs_2018-03-28-04-59-58.zip?authuser=1

[andrewtchin]

Based on review of the robot logs and talking with @matthewavery, we need the port layer log but the container-logs bundle was not gathered during this test suite.
The VCH create succeeds fully with the docker API check, but the test case immediately following setup and all subsequent ones fail to connect to the docker daemon.
The VCH appears to have disappeared.
May need to improve this test to gather the container-logs bundle in cases of failure.

[andrewtchin]

VCH log collection was hidden under NFS Volume Cleanup -> Nimbus Cleanup

[hickeng]

This seems like a total failure for the drone worker to be able to communicate with the VCH.

The VCH shows up and running with IP assigned and processes started (see VCH-0-7761-tether.debug) however there's not a single test in this set that was able to connect to it.

@mhagen-vmware I'd be inclined to write this off as part of the network issues from the backlevel NIC bios given the timeframe. Concur?

[mhagen-vmware]

Can't be. Nightly executor is not in Haas, it is in OneCloud

[andrewtchin]

add ping to test, see if logging can be improved

[andrewtchin]

and tracer t