Closed Bug 527904 Opened 16 years ago Closed 16 years ago

moz2-linux-slave22 (maybe others?) needs to accept ssh host key for dm-symbolpush01

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Unassigned)

References

()

Details

I guess this must be a new slave: Transferring symbols... ./dist/firefox-3.7a1pre.en-US.linux-i686.crashreporter-symbols.zip The authenticity of host 'dm-symbolpush01.mozilla.org (10.2.74.40)' can't be established. RSA key fingerprint is 7d:5b:5d:d0:0d:e0:b8:b1:b8:43:a1:3b:b6:26:c8:7b. Are you sure you want to continue connecting (yes/no)? command timed out: 1200 seconds without output, killing pid 13403 Isn't this something that could be automated, or stored in the ref image? It's not like ssh host keys should ever change. (And if they did, we wouldn't be any worse off having the old one hardcoded.) (Also, the Linux nightly for today needs to be respun, because that's where this happened.)
These slaves were recloned in bug 527692. I don't see anything about them being moved to production in that bug, so I dunno why they're there. I'm pulling them out of production and putting them back in staging for now.
Just talked to coop and he said they were ready for production, so I just swapped in the right keys and left them there.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.