862426 - Win64 machines come back without the updated production keys

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Armen [:armenzg]]

I currently established that to setup a production machine I have to run these steps [1] to add all the needed keys:
rmdir /S /Q .ssh
C:\mozilla-build\msys\bin\scp -o 'StrictHostKeyChecking no' -o 'BatchMode=no' -r  cltbld@bld-lion-r5-041:~/.ssh .ssh

This is not an urgent request and I am fine if we dupe with the ability to add the keys to a machine automatically.

I thought of filing it to keep track of the issue and find the way forward.

[1] https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave#Production

Comment 1

[Amy Rich [:arr] [:arich]]

The 2008R2 machines are not part of the domain, so unless you give us the keys ahead of time to put in the ts, there's no way to easily update them after the fact.  After we get w7 and xp stood up, 2008R2 is next on the list of imaging/config management processes we are going to completely overhaul (and join to the domain).

Comment 2

[Armen [:armenzg]]

I don't want to update all current imaged win64 machines.
I just want to fix it so when we image more machines we don't forget that we have to manually update the keys.
We have it documented on our side but we can miss it.

We can let this seat or close it once we see the 2008R2 revamp getting closer.

Comment 3

[Mark Cornmesser [:markco]]

This is completed for now. However, if the keys changed a new bug will need to be open.