Closed Bug 848944 Opened 13 years ago Closed 12 years ago

Please re-image the following staging test machines and remove the following network block

Categories

(Infrastructure & Operations :: DCOps, task)

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: waiting on talos-r3-fed-001)

For the network block it will probably need a Netops bug similar to bug 808043. I don't know if all of these staging machines actually have the block. talos-mtnlion-r5-002 talos-mtnlion-r5-003 talos-r3-fed-002 talos-r3-fed-010 talos-r3-fed64-001 talos-r3-fed64-002 talos-r3-w7-001 talos-r3-w7-002 talos-r3-w7-003 talos-r3-w7-010 talos-r3-xp-001 talos-r3-xp-002 talos-r3-xp-003 talos-r3-xp-010 talos-r4-lion-002 talos-r4-lion-003 talos-r4-lion-010 talos-r4-snow-001 talos-r4-snow-002 talos-r4-snow-003 Other slaves (which are currently booked) will be requested in another round: talos-mtnlion-r5-001 talos-mtnlion-r5-010 talos-r3-fed-001 talos-r3-fed64-010 talos-r4-lion-001
Depends on: 848951
I'm going to try to do all but the fedora ones and see how far I get.
Successful: talos-mtnlion-r5-002 talos-mtnlion-r5-003 talos-r4-lion-003 talos-r4-lion-010 talos-r4-snow-001 talos-r4-snow-002 talos-r4-snow-003 talos-r3-w7-001 talos-r3-w7-002 talos-r3-w7-003 talos-r3-w7-010 Couldn't reach: talos-r4-lion-002 talos-r3-xp-002 The other three XP hosts are being pains in the butt per usual. They keep failing on tasklist. I'm trying another install of the three I can reach now and will let it run overnight.
Will fixing the netflows make the installs work better?
The netflows hinder windows activation since we aren't using KMS on those boxes. It's not going to solve the problem with XP being a pita. I got talos-r3-xp-001 to install correctly, Still working on the other two that are reachable.
talos-r3-xp-010 is also done successfully. talos-r3-xp-003 looked like it might have finished successfully, but didn't actually come back up and is not reachable now. So, needs hands on from dcops: talos-r4-lion-002 talos-r3-xp-002 talos-r3-xp-003 talos-r3-fed-002 talos-r3-fed-010 talos-r3-fed64-001 talos-r3-fed64-002
For my own clarity, I'm waiting on these: > talos-mtnlion-r5-001 - booked > talos-mtnlion-r5-010 - booked > talos-r3-fed-001 - booked > talos-r3-fed-002 - IT working on it > talos-r3-fed-010 - IT working on it > talos-r3-fed64-001 - IT working on it > talos-r3-fed64-002 - IT working on it > talos-r3-fed64-010 - booked > talos-r3-xp-002 - IT working on it > talos-r3-xp-003 - IT working on it All the other machines have been setup to go in production once we have a reconfiguration.
I got talos-r3-xp-003 working.
talos-r3-fed64-010 and talos-mtnlion-r5-010 are now available to be re-imaged. These are still booked: > talos-mtnlion-r5-001 - booked > talos-r3-fed-001 - booked
Reimaged talos-mtnlion-r5-010 and talos-mtnlion-r5-001 (talked to kmoir). The following still need dcops intervention now: talos-r4-lion-002 talos-r3-xp-002 talos-r3-fed-002 talos-r3-fed-010 talos-r3-fed64-001 talos-r3-fed64-002 talos-r3-fed64-010
colo-trip: --- → scl1
Did anyone actually get to these in the scl1 trip yesterday?
Due to current workload, we're trying to limit non-emergency SCL1 trips to Tue & Thu. There should be more time to deal with them today.
The following hosts have been reimaged. talos-r3-xp-002 talos-r3-fed-002 talos-r3-fed-010 talos-r3-fed64-001 talos-r3-fed64-002 talos-r3-fed64-010 Talos-r4-lion-002 seemed to be hung during the imaging process. I let it run over night will check back in a bit.
talos-r4-lion-002 was complaining about an invalid disk selection during the imaging process. I tried rebooting it to restart deploystudio, but it's hard down again instead. I wonder if there's a bad disk. Could you run diags on it, please?
Talos-r4-lion-002 has a dead hard drive. :ashlee - Can you order a replacement hard drive for us? Stock hard drive is a Hitachi 320gb - 5400 rpm. Let's order 3 of them (2 to keep as spare).
3 Hitachi 320gb-5400 rpm HD's have been ordered and shipped to scl3. Order Number: 105-7085152-1739404
Can you please activate the win7 machines? talos-r3-w7-001 talos-r3-w7-002 talos-r3-w7-003 talos-r3-w7-010
I made sure they were all activated.
Armen: is talos-r3-fed-001 still booked?
(In reply to Amy Rich [:arich] [:arr] from comment #18) > Armen: is talos-r3-fed-001 still booked? jhopkins says that we can take it back and proceed with this. Is there a bug or ticket for the HD replacement for talos-r4-lion-002? I want to add it as a dependency. FYI, all other machines are working well.
Depends on: 852833
Hard drive has been replaced for talos-r4-lion-002. Host has been reimaged.
Hi, Any theories on what could be different on the 4 Windows 7 machines? They fail certain tests and I have not been able to determine what could be different on them (they seem to have the dongles). I am running out of ideas.
I'm setting talos-r4-lion-002 up. Is talos-r3-fed-001 ready to be set up?
DCOps: if we reimage talos-r3-fed-001, this bug can be closed.
Whiteboard: waiting on talos-r3-fed-001
talos-r3-fed-001 has been reimaged.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.