Ok, cb-seamonkey-win32-01 should be ready for refimage creation. Before we deploy the refimage to the other parallels VM's for this setup, I want to actually start up the VM to my production for a few days, incase something is off/missed something/etc. So I can try and catch any issues while its easier to fix. Notes: * The machine has static IP set, and is not querying via DHCP (none of our win machines are). * The machine has a shorter "Computer Name" set (due to discovered NetBIOS issues, but this should still work fine with the current jumphost DNS CNAME) * Has no ssh keys/config/known-hosts on it. * Has no buildbot.tac * Has buildbotve setup already. * Not yet actually run as a builder, so /e/builds is empty except for folders. Chose not to set 3G RAM boot settings until I understand more carefully the RAM available on the HOST system.
cb-seamonkey-win32-01 is not listed in inventory and as such I will need to know where it is located so I can update inventory and grab an image off of it.
Status: NEW → ASSIGNED
cb-seamonkey-win32-01 is on bm-parallels01 I will get this ref image as soon as possible.
I was wrong it is on cb-parallels01
I was able to power up 02 and 03 today and both were verified as working by Callek. I made a copy of 01's pvm file and am backing it up to FS02 in case we lose the raid again.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(In reply to Matthew Larrain[:digipengi] from comment #4) > I was able to power up 02 and 03 today and both were verified as working by > Callek. I made a copy of 01's pvm file and am backing it up to FS02 in case > we lose the raid again. For sake of argument can you note (here or to me directly) where this is being stored on FS02 incase in the future someone other than you needs to find it?
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.