472540 - rename moz2-win32-slave1

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Once the new moz2-win32-slave01 is available, we can delete moz2-win32-slave1. This makes the names of slaves in the pool consistent. 

Instead of rechecking the slave is identical to ref image, and munging dns/nagios/etc, lets just delete/reclone the VM as we're creating othere new clones anyway.

Comment 1

[[e-mail] (:bhearsum)]

I really don't understand why we're going to go to the trouble of deleting this machine when all we need to do is change it's DNS and hostname. If we're truly worried about inconsistencies we should delete all of the linux & windows slave01 through slave06 - as they were the first batch of slaves.

There's been no evidence to suggest inconsistency, however. Will anyone yelp loudly if I simply change the name and be done with it?

Comment 2

[[e-mail] (:bhearsum)]

I'll take care of renaming this tomorrow.

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Ben and I talked about this on phone this afternoon - he'd done the original setup of this machine, and its been working fine, so made good points about machine being good as-is, and it being faster to just rename.

(thanks Ben for taking this).

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

rats - missed removing the dependency with last comment. sorry for bugspam.

Comment 5

[[e-mail] (:bhearsum)]

Attachment: rename moz2-win32-slave1 to moz2-win32-slave01

Comment 6

[[e-mail] (:bhearsum)]

Comment on attachment 355966 [details] [diff] [review]
rename moz2-win32-slave1 to moz2-win32-slave01

changeset:   651:dd24cd5a754a

Comment 7

[[e-mail] (:bhearsum)]

This is all completed now.