-
Notifications
You must be signed in to change notification settings - Fork 175
Closed
Labels
area/dockerSupport for the Docker operationsSupport for the Docker operationspriority/p1source/scenarioFound via a scenario failureFound via a scenario failureteam/container
Description
04/30/18, VC 6.5, 5-25-OPS-User-Grant
Test case: vic-machine configure grants ops-user perms, Run privilege-dependent docker operations
command:
docker -H sc2-rdops-vm08-dhcp-12-197.eng.vmware.com:2376 --tls pull busybox 2>&1
return code is 143. Output:
Using default tag: latest
latest: Pulling from library/busybox
f70adabe43c0: Pulling fs layer
a3ed95caeb02: Pulling fs layer
a3ed95caeb02: Verifying Checksum
a3ed95caeb02: Download complete
f70adabe43...
It seems that the container was unexpectedly stopped/exited.
On that day PR #7874 was not merged yet, so there was still a bug in the robot test that the container logs and appliance logs for the VCH were not collected. Without those logs, it's hard to diagnose what happened. We might want to de-prioritize this and wait until a re-pro.
Link: https://storage.cloud.google.com/vic-ci-logs/vic_nightly_logs_2018-04-30-00-29-07.zip?authuser=1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/dockerSupport for the Docker operationsSupport for the Docker operationspriority/p1source/scenarioFound via a scenario failureFound via a scenario failureteam/container