Closed
Bug 1531208
Opened 6 years ago
Closed 6 years ago
Interactive tasks fail with /.taskclusterutils/busybox: no such file or directory
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glandium, Assigned: wcosta)
References
Details
Attachments
(1 file)
[taskcluster 2019-02-28 02:18:39.929Z] Task ID: e-lWueleSkiLRIhkfbV3tA
[taskcluster 2019-02-28 02:18:39.929Z] Worker ID: i-00427aa4a174cc31f
[taskcluster 2019-02-28 02:18:39.929Z] Worker Group: us-east-1
[taskcluster 2019-02-28 02:18:39.929Z] Worker Node Type: m5.4xlarge
[taskcluster 2019-02-28 02:18:39.929Z] Worker Type: gecko-1-b-android
[taskcluster 2019-02-28 02:18:39.929Z] Public IP: 3.80.12.203
[taskcluster 2019-02-28 02:18:40.912Z] Image 'public/image.tar.zst' from task 'T3OYM8KfRE2fq8cVQDeYGg' loaded. Using image ID sha256:5b0d66e29ab28ae361581f9ffe62d651779adc3948318400fa85c5161c326021.
[taskcluster 2019-02-28 02:18:40.927Z] === Task Starting ===
[taskcluster:error] Failure to properly start execution environment.
[taskcluster:error] (HTTP code 400) unexpected - OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/.taskclusterutils/busybox\": stat /.taskclusterutils/busybox: no such file or directory": unknown
[taskcluster 2019-02-28 02:18:41.560Z] === Task Finished ===
[taskcluster 2019-02-28 02:18:41.560Z] Unsuccessful task run with exit code: -1 completed in 1.631 seconds
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Comment 1•6 years ago
|
||
Wander's PR.
Comment 2•6 years ago
|
||
Rolled out to production.
Release: https://github.com/taskcluster/docker-worker/releases/tag/v201902281053
Assignee | ||
Comment 3•6 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 4•6 years ago
|
||
The rollout caused a bustage due to invalid CoT keys.
I'm currently making a new deployment with the updated CoT keys...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•6 years ago
|
||
Deployment completed.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•