Bug 1090577 (t-w864-ix-163)

t-w864-ix-163 problem tracking

RESOLVED FIXED

Status

Infrastructure & Operations
CIDuty
P3
normal
RESOLVED FIXED
4 years ago
a month ago

People

(Reporter: coop, Unassigned)

Tracking

Details

(Whiteboard: [buildduty][buildslaves][capacity])

(Reporter)

Description

4 years ago
Doesn't appear to be in DNS.
https://inventory.mozilla.org/en-US/systems/show/8360/
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 2

4 years ago
Let me be more precise:

(buildduty)xebec:js ccooper$ nslookup t-w864-ix-162
Server:         10.22.75.40
Address:        10.22.75.40#53

t-w864-ix-162.build.mozilla.org canonical name = t-w864-ix-162.wintest.releng.scl3.mozilla.com.
Name:   t-w864-ix-162.wintest.releng.scl3.mozilla.com
Address: 10.26.41.227

(buildduty)xebec:js ccooper$ nslookup t-w864-ix-163
Server:         10.22.75.40
Address:        10.22.75.40#53

** server can't find t-w864-ix-163: NXDOMAIN

The CNAME for t-w864-ix-163 doesn't appear to be correct, which prevents buildbot from connecting. I'll admit, it *does* look correct in inventory though.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(Reporter)

Comment 3

4 years ago
It's connected and taking jobs now. Thanks!
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Added by bug 1088839 but running at a too-small resolution. Disabled in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Updated

4 years ago
Depends on: 1088839

Updated

4 years ago
Depends on: 1091708

Updated

4 years ago
No longer depends on: 1088839
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
bkelly noticed that this slave was one of the only ones still hitting bug 1160013 on a regular basis. Disabled for diagnostics.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Updated

3 years ago
Depends on: 1178007
(Reporter)

Comment 6

3 years ago
Returned to production.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago3 years ago
Resolution: --- → FIXED
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #5)
> bkelly noticed that this slave was one of the only ones still hitting bug
> 1160013 on a regular basis. Disabled for diagnostics.

Still hitting bug 1160013.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-imaged and returned to production. Also, it started taking jobs.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED

Updated

a month ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.