Closed Bug 1231111 Opened 9 years ago Closed 8 years ago

Taskcluster jobs fail with ''wget: unable to resolve host address `s3-copy-proxy-us-west-1.taskcluster.svc.tutum.io'

Categories

(Taskcluster :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1241442

People

(Reporter: aryx, Assigned: garndt)

Details

E.g. https://treeherder.mozilla.org/#/jobs?repo=b2g-inbound&revision=2bdd9ec79799
with https://public-artifacts.taskcluster.net/HBxKGaU5SsaV8Zfo5GDYFw/0/public/logs/live_backing.log

Location: http://s3-copy-proxy-us-east-1.taskcluster.svc.tutum.io/Y9DtZzSdS9ecyp-RIwXkXQ/1/public/build/mozharness.zip [following]
--2015-12-08 11:58:22--  http://s3-copy-proxy-us-east-1.taskcluster.svc.tutum.io/Y9DtZzSdS9ecyp-RIwXkXQ/1/public/build/mozharness.zip
Resolving s3-copy-proxy-us-east-1.taskcluster.svc.tutum.io (s3-copy-proxy-us-east-1.taskcluster.svc.tutum.io)... failed: Name or service not known.
wget: unable to resolve host address `s3-copy-proxy-us-east-1.taskcluster.svc.tutum.io'
seems this is fixed now, reopen the trees now, leaving the bug open in case someone will take into this what happened here
Severity: blocker → normal
I hopped on some hosts, but it seemed to be after the blip.  This appeared to be an issue with tutum.io address resolution so I think this was a blip on tutum's end.  Looks like it came back up and jobs started turning green again.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee: nobody → garndt
Happening now again...

http://status.tutum.co/ reports no problems...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This is now being tracked in bug 1241442
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.