Closed Bug 661758 Opened 13 years ago Closed 13 years ago

add w32-ix-slave{07,08} to production_config.py

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

(Whiteboard: [slaveduty][badslave?])

Attachments

(1 file)

These hosts used to be staging, but have been re-imaged and there's no good reason to keep them in the staging pool.  They're already pointed at build hosts by slavealloc, and have the right SSH keys, but aren't in the production configs, it seems.  Please update and land the change.
Attached patch as requestedSplinter Review
Attachment #537503 - Flags: review?(dustin)
Attachment #537503 - Flags: review?(dustin) → review+
Assignee: nobody → aki
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
enabled and rebooted - these should be building soon.
Reopening, due to bug 656572 comment #3. I'm guessing the ref image is missing updates, and/or OPSI needs some packages marked for install. Disabled them both in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: aki → nobody
Whiteboard: [buildmasters] → [slaveduty][badslave?]
Priority: -- → P3
Assignee: nobody → dustin
So far, affected are
 w32-ix-slave07 (bug 656572)
 w32-ix-slave08 (bug 656572)
 w32-ix-slave34 (bug 662853)
So I think that this is caused by the use of a moving tag as the "version" for the buildbot package in OPSI.  the refimage has the old version in it, which is odd in itself, but since we don't specify a particular version, it doesn't even get updated.  I've updated the refimage, and will set the above w32-ix-* slaves to setup buildbot version BUILDBOT_PRODUCTION.  If that seems successful, I'll do the same for all w32-ix slaves, to catch any stragglers (since OPSI has no way to distinguish versions of buildbot).
It was more complicated than that:
 w32-ix-slave07 was inventing the incorrect OPSI key for itself
 w32-ix-slave08 was pretty easy
 w32-ix-slave34 doesn't seem to have a good instal of mozillabuild, so I'm re-installing that, and it's taking forever.  So that's where we are.  None of the hosts are enabled yet, but 07 and 08 should be ready to go.
Status: REOPENED → ASSIGNED
w32-ix-slave{07,08} are doing fine, and have been rebooted back into action.

w32-ix-slave34 has been stuck since the 9th at the installing-MozillaBuild screen, and is now wedged.  I'll get a re-image started back on bug 662853.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
07 and 08 are *not* fine - they do not have nagios installed.

I'm done with OPSI.  I'll install this package by hand.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
fixed with vim - they had an old version of NSC.ini.
And fixed on the ref box, too.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Many w32 ix machines have been having issues in the last few months. Several of them will be reimaged and setup correctly in bug 682408.
Blocks: 682408
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: