Closed Bug 1187941 Opened 9 years ago Closed 9 years ago

docker-worker fails with "Artifact already exists" for a task without artifacts declared

Categories

(Taskcluster :: Workers, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: rail, Assigned: garndt)

References

Details

See https://tools.taskcluster.net/task-inspector/#OnUZHJK8QwqTXfz_HRodfg/1 The task itself doesn't declare any artifacts. It only has the logs as artifacts. [taskcluster] taskId: OnUZHJK8QwqTXfz_HRodfg, workerId: i-793421aa [taskcluster] Error: Task was aborted because states could not be created successfully. Error: Error: Artifact already exists, with different type or later expiration [taskcluster] Unsuccessful task run with exit code: -1 completed in 61.672 seconds
Currently I'm unsure where this issue is coming from so we are going to be adding some additional information both in the queue when the artifact already exists as well as outputting that in the worker debug logs. the queue piece of this is here: https://github.com/taskcluster/taskcluster-queue/commit/5262ee6751f39ec59dc6e25e50abaad661a59bcb
Assignee: nobody → garndt
I've been monitoring this for a little bit and haven't had reports of any issues. We now have debug output from the queue about the original artifact and the new artifact that's trying to be created to get more information about this scenario. Rail, have you seen this issue again? If not, I think this might have just been a disturbance in the forced at the time and we could close this for now.
Flags: needinfo?(rail)
I saw 3-4 occurrences yesterday. If you want, I can post them here when they happen.
Flags: needinfo?(rail)
If there are more recent examples that would be helpful. Thanks!
Oops. ignore that
(In reply to Rail Aliiev [:rail] from comment #3) > I saw 3-4 occurrences yesterday. If you want, I can post them here when they > happen. You can ignore the statement above. I mixed it with other signatures (ECONRESET and socket hung up). I'd say I haven't seen this signature for weeks. RESOLVED FIXEDSOMEHOW?
Could be that I started publishing artifacts for that task type...
Hrm, odd. I'm not sure what might have magical fixed this, but I'm glad to see that this hasn't come up again. If you feel comfortable closing this for now, feel free.
Yeah, let's close it. I'll reopen if see something.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Component: Docker-Worker → Workers
You need to log in before you can comment on or make changes to this bug.