Closed Bug 1299457 Opened 9 years ago Closed 8 years ago

Intermittent [taskcluster:error] Docker configuration could not be created. This may indicate an authentication error when validating scopes necessary for running the task.

Categories

(Taskcluster :: Workers, defect)

Product:
Taskcluster
Component:
Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Assigned: dustin)

References

Details

(Keywords: intermittent-failure)

Appears this was starred once so i'm thinking a bad machine. I haven't seen it reported again and we've been adjusting apparmor profiles for many months.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Happens ~1/week.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Ten times since Aug 31, so 0.7/wk. https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1299457&entireHistory=true&tree=all It looks like it always affects android-4-3-armv7-api15 tests, I think because those are one of the few places we use task-retry for automatically retrying intermittent jobs. The error is [taskcluster:error] Docker configuration could not be created. This may indicate an authentication error when validating scopes necessary for running the task. Error: Command failed: /bin/sh -c apparmor_parser -a /etc/apparmor.d/worker-fnpufUN_TzO7BwyJPRXn_Q apparmor_parser: Unable to add "worker-fnpufUN_TzO7BwyJPRXn_Q". Profile already exists which suggests that just adding the runId to that name might be sufficient.
Assignee: nobody → dustin
Component: General → Docker-Worker
Commits pushed to master at https://github.com/taskcluster/docker-worker https://github.com/taskcluster/docker-worker/commit/98350a823b1e7496ac791d749f6d068424ea8215 Bug 1299457: include runId in apparmor profile name This avoids conflicts if a task is re-run on the same instance. https://github.com/taskcluster/docker-worker/commit/29f90ddb2f8b92908e98ae3bd2e479b8b2dae788 Merge pull request #273 from taskcluster/bug1299457 Bug 1299457: include runId in apparmor profile name
I believe this is getting deployed to workerTypes now -- starting with gecko-t-linux-medium.
Definitely deployed now, and working.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
Resolution: --- → FIXED
See Also: → 1481974
Component: Docker-Worker → Workers
You need to log in before you can comment on or make changes to this bug.