Closed
Bug 684019
(b-2008-ix-0182)
Opened 13 years ago
Closed 9 years ago
b-2008-ix-0182 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslave][capacity])
This was the hardware's original purpose, anyway.
Updated•13 years ago
|
Blocks: support-win64
Reporter | ||
Comment 1•13 years ago
|
||
winbuild dhcp - check
removed from netops dhcp - check
winbuild dns - check
removed from netops dns - check
(along with some other w64-ix-slaveNN in incorrect PTR records)
bmo cnames added - check
reimage - in progress
Reporter | ||
Comment 2•13 years ago
|
||
reimage complete -- over to releng.
Assignee: dustin → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Updated•13 years ago
|
Assignee: nobody → armenzg
Comment 3•13 years ago
|
||
w64-ix-slave41 got fixed in bug 673972 and will use this bug to track putting it back to the pool.
Status: NEW → ASSIGNED
Summary: re-image scl-production-puppet-old as w64-ix-slave05 → re-image scl-production-puppet-old as w64-ix-slave05 & add w64-ix-slave41 back to the pool
Comment 4•13 years ago
|
||
and w64-ix-slave04 from bug 679818.
Status: ASSIGNED → NEW
Priority: -- → P2
Summary: re-image scl-production-puppet-old as w64-ix-slave05 & add w64-ix-slave41 back to the pool → re-image scl-production-puppet-old as w64-ix-slave05 & add w64-ix-slave{04,41} back to the pool
Updated•13 years ago
|
Priority: P2 → P3
Comment 5•13 years ago
|
||
#4 was re-imaged in bug 679818 but can't reach it.
#5 is being used by coop in his staging machine.
#41 is being used by digipengi in bug 683976.
Summary: re-image scl-production-puppet-old as w64-ix-slave05 & add w64-ix-slave{04,41} back to the pool → add w64-ix-slave{04,05,41} back to the pool
Comment 6•13 years ago
|
||
#4 can now be reached. It should be added to producton_config.py and slave-alloc.
I wouldn't cry if any of these slaves were re-imaged as w32 slaves.
Assignee: armenzg → nobody
Comment 7•13 years ago
|
||
I'm reserving #5 for dev testing so please don't recycle it back to the prod pool.
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Machine Management
Whiteboard: [buildduty][buildslave][capacity]
Comment 8•13 years ago
|
||
(In reply to John Hopkins (:jhopkins) from comment #7)
> I'm reserving #5 for dev testing so please don't recycle it back to the prod
> pool.
Could you file a new bug when you're ready to give w64-ix-slave05 back?
I'm going to ask digipengi the same thing re: w64-ix-slave41, and act on the only actionable slave here (w64-ix-slave04).
Updated•13 years ago
|
Alias: w64-ix-slave04
Summary: add w64-ix-slave{04,05,41} back to the pool → w64-ix-slave04 problem tracking
Comment 9•13 years ago
|
||
Imaged, set to preprod in slavealloc, and rebooted. We'll see where this goes I suppose.
Comment 10•13 years ago
|
||
buildbot was busted. I re-installed as per https://wiki.mozilla.org/ReferencePlatforms/Win64#Buildbot and it seems to be working now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 11•13 years ago
|
||
Reopening for a post-loan reimage after bug 760141.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•13 years ago
|
No longer blocks: support-win64
Comment 12•12 years ago
|
||
Back to dev/pp pool.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 12 years ago
Resolution: --- → FIXED
Comment 13•12 years ago
|
||
I'm marking this as disabled in slavealloc due to:
Thu 19:57:08 PDT [491] w64-ix-slave04.winbuild.scl1.mozilla.com:disk - E is UNKNOWN: UNKNOWN: Drive is not a fixed drive: E: (it is a CDROM drive) (http://m.allizom.org/disk+-+E)
That looks interestingly scary to me.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 14•12 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #13)
> I'm marking this as disabled in slavealloc due to:
....
O was already marked as disabled in slavealloc with a note that its loaned to :dustin -- CC'ed him here for sanity
Updated•12 years ago
|
Whiteboard: [buildduty][buildslave][capacity] → [buildduty][buildslave][capacity][loaned to dustin]
Comment 15•12 years ago
|
||
Re-image requested on bug 855053.
Whiteboard: [buildduty][buildslave][capacity][loaned to dustin] → [buildduty][buildslave][capacity]
Reporter | ||
Comment 16•12 years ago
|
||
That note was from a long time ago - it wasn't removed by whoever processed the loan return.
Comment 17•12 years ago
|
||
Back in preprod.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 18•11 years ago
|
||
In l10n repacks for a staging release, I was hitting:
command: START
command: rm -rf
/c/builds/moz2_slave/rel-m-beta-w32_rpk_1-000000000/mozilla-beta/obj-l10n/dist/previous
command: cwd: c:\builds\moz2_slave\rel-m-beta-w32_rpk_1-000000000
command: output:
command: END (0.00s elapsed)
command: START
command: mkdir
/c/builds/moz2_slave/rel-m-beta-w32_rpk_1-000000000/mozilla-beta/obj-l10n/dist/previous
command: cwd: c:\builds\moz2_slave\rel-m-beta-w32_rpk_1-000000000
command: output:
mkdir: cannot create directory
`/c/builds/moz2_slave/rel-m-beta-w32_rpk_1-000000000/mozilla-beta/obj-l10n/dist/previous':
File exists
ie silent failure to delete a directory.
Buildduty, could you please do the magic to get this reimaged, staying a staging slave.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 19•11 years ago
|
||
reimage complete, just rebooted it --> "fixed" and back in staging
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Alias: w64-ix-slave04 → b-2008-ix-0182
Summary: w64-ix-slave04 problem tracking → b-2008-ix-0182 problem tracking
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 20•10 years ago
|
||
Enabled and rebooted.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•9 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
QA Contact: bugspam.Callek
Resolution: --- → FIXED
Comment 22•9 years ago
|
||
deallocated from bug 1198317
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Comment 23•9 years ago
|
||
Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 1219106)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•9 years ago
|
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 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
•