Please re-image the XP machines moved to the Win 8 pool

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: alin.selagea, Assigned: arich)

Tracking

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
In bug 1317723 we're moving 162 XP machines to Win 8. The following actions will be needed to those:
  - rename + re-image
  - nagios updates
  - inventory updates
(Reporter)

Comment 1

2 years ago
t-xp32-ix-061
t-xp32-ix-062
t-xp32-ix-063
..
..
t-xp32-ix-221
t-xp32-ix-222

will become

t-w864-ix-236
t-w864-ix-237
t-w864-ix-238
..
..
t-w864-ix-396
t-w864-ix-397
(Assignee)

Comment 3

2 years ago
There's still a problem with invtool, so this is blocked on getting some assistance from IT.
Assignee: relops → arich
(Assignee)

Comment 4

2 years ago
Initial issues with invtool was that exporting from the google sheet used the wrong line termination. Modified the exported file to use CR/LF and split the import up into batches of 25 (otherwise it would fail).

Nagios update made in git:
   080eefe..7ae987b  master -> master
(Assignee)

Comment 5

2 years ago
And gcox showed me how to delete the filename kv from the SREG of the machines. Start with a file of ips (one per line) of each host you want to delete the filename kv from:

for IP in `cat file-with-ips`; do ./inv HW_kv list --obj-pk `./inv search -q "type=:HWadapter AND hwadapter.sreg__ip_str=$IP" | head -1 | awk '{print $1}'` | grep -B1 'key: filename' | head -1 | awk '{print $3}' >> filename-pks; done

for PK in `cat filename-pks`; do ./inv HW_kv delete --kv-pk $PK; done
(Assignee)

Comment 6

2 years ago
I've started reimaging these in batches of 20. Those I've kicked off a reimage on are in orange in https://docs.google.com/spreadsheets/d/1I38-lTHwaxjS1pPjLxmzCM9cTQuFw9bkuN-ADsKEIiE/edit#gid=1809836447
(Assignee)

Comment 7

2 years ago
All machines have been rebooted after setting the bootdev to pxe and are now pingable again. :markco spot checked the first few and thought they looked okay, but buildduty may want to do a more thorough check before enabling them all.
Flags: needinfo?(aselagea)
Flags: needinfo?(aobreja)
Created attachment 8812161 [details]
wrong_resolution.PNG

All machines seems fine except those from bellow:

t-w864-ix-244  (is seen as xp32-ix-069)
t-w864-ix-297 (is seen as t-xp32-ix-122)
t-w864-ix-301 (wrong resolution 1024x768 ,only monitor 1 generic Non Pnp available)
t-w864-ix-316 ( seen as t-xp32-ix-141)
t-w864-ix-341 (wrong resolution 1024x768 ,only monitor 1 generic Non Pnp available)
t-w864-ix-353 (wrong resolution 1024x768 ,only monitor 1 generic Non Pnp available)
t-w864-ix-361 (wrong resolution 1024x768 ,only monitor 1 generic Non Pnp available)

Attached is a machines with a wrong resolution.
Flags: needinfo?(aselagea)
Flags: needinfo?(aobreja)
After been re-imaged all machines look fine.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.