Closed
Bug 896621
(t-xp32-ix-005)
Opened 11 years ago
Closed 6 years ago
t-xp32-ix-005 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslaves][capacity])
No description provided.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Assignee: nobody → armenzg
Comment 1•11 years ago
|
||
Waiting to be re-imaged. After re-imaging they can do directly into the pool.
Assignee: armenzg → nobody
Comment 2•11 years ago
|
||
Back into production.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 3•8 years ago
|
||
Bug 1302927 broken, disabled.
Status: RESOLVED → REOPENED
Depends on: 1302927
QA Contact: armenzg → bugspam.Callek
Resolution: FIXED → ---
Comment 4•8 years ago
|
||
Back online and taking jobs.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Comment 5•6 years ago
|
||
Hi Van, this machine looks to be broken and there are currently 70 pending tests for them, can you take a look at it?
Status: RESOLVED → REOPENED
Flags: needinfo?(vle)
Resolution: FIXED → ---
Comment 6•6 years ago
|
||
the machine is currently disabled on slave allocator. Van please check the machine state. Thank you
Comment 7•6 years ago
|
||
host is back online after reboot. [vle@admin1a.private.scl3 ~]$ fping t-xp32-ix-005.wintest.releng.scl3.mozilla.com t-xp32-ix-005.wintest.releng.scl3.mozilla.com is alive
Flags: needinfo?(vle)
Comment 8•6 years ago
|
||
I enabled it back, ci-duty will monitor it to see the state of it. Thank you.
Comment 9•6 years ago
|
||
I have also restarted it, but it doesn't takes jobs. The machine is still broken. I will disable it again. Van can you please take a look at it?
Flags: needinfo?(vle)
Comment 10•6 years ago
|
||
I've just checked once more the machine on slave health and it seems it has received a job, today. I have enabled it and we will continue monitoring it.
Comment 11•6 years ago
|
||
The machine is taking and successfully running tasks. This bug can be closed since the machine is healthy.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 6 years ago
Flags: needinfo?(vle)
Resolution: --- → FIXED
Comment 12•6 years ago
|
||
Hello, This machine looks broken again, and it didn't send any logs since Jul 01 23:19:56. Van can you take a look at it and give it a reboot? Also, it has been disabled in slavealloc. Thank you.
Status: RESOLVED → REOPENED
Flags: needinfo?(vle)
Resolution: FIXED → ---
Comment 14•6 years ago
|
||
Thank you, Van. The machine is enable in slavealloc now. I'm waiting to takes jobs.
Comment 15•6 years ago
|
||
(In reply to Radu Iman[:riman] from comment #14) > Thank you, Van. The machine is enable in slavealloc now. I'm waiting to > takes jobs. I don't believe it's going to take jobs soon, currently it's not attached to any master..
Comment 16•6 years ago
|
||
Back in the day, when triggering a reboot from slave health actually worked, that just meant you needed one more reboot: the one while it was disabled got it healthy, but disabled and not trying to connect, and after enabling it it would take another reboot where it would come up seeing that it was enabled to get it to attach and start taking jobs.
Comment 17•6 years ago
|
||
Rebooted the machine, currently it attached to buildbot-master109.bb.releng.scl3.mozilla.com, waiting to take jobs
Comment 18•6 years ago
|
||
That worked.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•