Closed
Bug 1187934
Opened 9 years ago
Closed 8 years ago
docker-worker fails to initialize with EHOSTUNREACH
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [docker-worker])
Sounds like it's trying to initialize the link, but fails. Probably should be an infra error, so TC reschedules the task.
[taskcluster] taskId: 6bXVckMCRwysHlqkXA_jQQ, workerId: i-39808aea
[taskcluster] Error: Task was aborted because states could not be created successfully. Error: Error: connect EHOSTUNREACH
[taskcluster] Unsuccessful task run with exit code: -1 completed in 96.061 seconds
Updated•9 years ago
|
Whiteboard: [balrog-vpn-proxy]
Updated•9 years ago
|
Whiteboard: [balrog-vpn-proxy] → [docker-worker]
Updated•9 years ago
|
Component: Docker-Worker → Worker
Comment 1•8 years ago
|
||
I have not heard of this being reported in awhile. Going to close it for now until we have some more recent error reports to add to this bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•6 years ago
|
Component: Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•