Closed
Bug 493201
Opened 16 years ago
Closed 16 years ago
delete and reclone moz2-win32-slave08 from the ref image
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: jhford)
Details
This machine has been acting up and no amount of clobbering/rebooting has fixed it - let's just reclone it.
Comment 1•16 years ago
|
||
When we re-create it, let's give it a large (80 GB?) NTFS drive with ala bug 489940.
Interestingly, this slave had the new NTFS drive on it. I wonder if the filesystem is corrupted?
Updated•16 years ago
|
Assignee: server-ops → phong
Comment 2•16 years ago
|
||
VM deleted. I'm about the redeploy from ref image.
Comment 3•16 years ago
|
||
new VM is online with 80 GB NTFS drive with tweaks added.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 4•16 years ago
|
||
Need to update tar.exe on this machine before adding it to the build pool. See bug 383136 for details.
Assignee: phong → catlee
Status: RESOLVED → REOPENED
Component: Server Operations → Release Engineering
Resolution: FIXED → ---
Comment 5•16 years ago
|
||
John, can you do this as you are already working on bug#493341?
Assignee: catlee → jford
OS: Mac OS X → Windows Server 2003
Assignee | ||
Comment 6•16 years ago
|
||
done
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Comment 7•16 years ago
|
||
Tar may be updated, but nagios says this machine hasn't reported to the buildbot master in 23 days. What's up here ?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•16 years ago
|
||
It seems that this machine doesn't have buildbot at all.
I am going to check if the post ref-image steps were done
Assignee | ||
Comment 9•16 years ago
|
||
I am going to move this machine to production at the same time as the machines in bug 492928
OPSI is installed and configured correctly and I have created a buildbot slave on this machine.
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 10•16 years ago
|
||
sorry for the bugmail spam, i meant to say bug 500763
Assignee | ||
Comment 11•16 years ago
|
||
fixed and has been in production. see bug in comment 10 for details
Status: ASSIGNED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 12•16 years ago
|
||
Looks like something is up with OPSI - it said "401 unauthorized" when i rebooted it today. John, do you have time to look into that?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•16 years ago
|
||
I had a go at resolving this and won in the end. An uninstall/reinstall by following
https://wiki.mozilla.org/ReferencePlatforms/Win32#OPSI_Setup
didn't work. Eventually traced the problem by diffing registry and disk install against a working machine. win32-slave08 was ending up with this in c:\program files\opsi.org\cfg\locked.cfg:
[shareinfo]
pckey={"message":"Cannot find opsiHostKey for host 'win32-slave08.uib.local' in file '/etc/opsi/pckeys'","class":"BackendMissingDataError"}
After going "OpsiClient > Create new opsi client", putting only "win32-slave08" in the Client name box, then an install on the slave worked. It's ended up with the MAC address not recorded but that's probably fine as we're not using the OPSI server for DHCP.
I'm not sure what to recommend for the future, since the initial state isn't known. It's possible that the opsi-admin command needs amending - the -d part seems strange if opsiconfd is master daemon for querying.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•