Alin Selagea [:aselagea] Reporter
	Description • 8 years ago

Noticed today that t-xp32-ix-002 was running Windows 8 instead of XP and its name was T-W864-AWS-BAS. I did a re-image, but that also installed Windows 8. Moreover, at the moment I'm not able to connect to the machine via vnc or ssh (the KVM console works though). The same thing goes for t-xp32-ix-011.

	Amy Rich [:arr] [:arich]
	Comment 1 • 8 years ago

Did t-xp32-ix-002 start running w8 after a reimage today, or has it been like this for longer?

	Alin Selagea [:aselagea] Reporter
	Comment 2 • 8 years ago

(In reply to Amy Rich [:arr] [:arich] from comment #1)
> Did t-xp32-ix-002 start running w8 after a reimage today, or has it been
> like this for longer?

t-xp32-ix-002 has been re-imaged twice during the last two days (I'm not sure what OS was running before that). t-w864-ix-025 also got re-imaged today, the strange thing is that it now thinks it's T-W864-AWS-BAS (the same as the XP slaves mentioned above).

	Q Assignee
	Comment 3 • 8 years ago

Rules.ini corrected and machines can now reimage correctly. t-xp32-ix-002 was reimaged as a test and is almost complete.

	Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]
	Comment 4 • 8 years ago

Tried today to re-image t-w864-ix-025 and t-xp32-ix-011 but  still get the same problem.

	Mark Cornmesser [:markco] OOO 2024/04/15
	Comment 5 • 8 years ago

I rebooted wds1 since it was showing an error stating that the rules.ini file was open. After the reboot, I reimaged t-xp32-ix-011, and it came up with the correct OS.

	Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]
	Comment 6 • 8 years ago

Re-imaged t-xp32-ix-011 and t-w864-ix-025,the OS and name of the slaves are ok now,also re-enabled in slavealloc and the slaves are taking jobs.