Closed
Bug 816097
Opened 12 years ago
Closed 11 years ago
a bunch of w64 slaves have the wrong set of keys
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
Here's what w64-ix-slave79 looks like, which isn't able to upload xrbld stuff to symbols1: C:\Users\cltbld\.ssh>md5sum * 7a4462e3622ec1c00868e09e0ebe2199 *authorized_keys 296299bed50fed2c37e03b9d9e05090e *cltbld_dsa 7e710598aa9ca70820280bae94eb287c *cltbld_dsa.pub 7849f10777121e1d0509f070b411506b *config 63da02ef4876768add93cf15866c406a *cvs 44b2078b6ae0e579790a68b9787046f8 *cvs.pub f9caa02330488a58cb1caf9563176ec9 *environment 166b900d8ef53ef5a1bb908904083444 *ffxbld_dsa 22d81d41b9034bdd945deffc60054f15 *ffxbld_dsa.pub 296299bed50fed2c37e03b9d9e05090e *id_dsa 7e710598aa9ca70820280bae94eb287c *id_dsa.pub 6680d0557b311dbe3f3991e1ae64ce8a *known_hosts 9bd827ca4990bcb90a9f20d64e31e1b4 *xrbld_dsa 0df8a33aa74fab044a22372cfebe79ea *xrbld_dsa.pub And here's what w64-ix-slave12 looks like, which _is_ able to: C:\Users\cltbld\.ssh>md5sum * 4bb519d9d89c85b11c987b00a8681154 *auspush 7a4462e3622ec1c00868e09e0ebe2199 *authorized_keys 372aadadf402df3790ce46690b285fd0 *calbld_dsa 75e8750087748b160c8b5f26c2c52f44 *calbld_dsa.pub 296299bed50fed2c37e03b9d9e05090e *cltbld_dsa 7e710598aa9ca70820280bae94eb287c *cltbld_dsa.pub 7849f10777121e1d0509f070b411506b *config 63da02ef4876768add93cf15866c406a *cvs 44b2078b6ae0e579790a68b9787046f8 *cvs.pub 2ca69a8e316ebfce757ee31ec14bcdf5 *environment 166b900d8ef53ef5a1bb908904083444 *ffxbld_dsa 22d81d41b9034bdd945deffc60054f15 *ffxbld_dsa.pub 296299bed50fed2c37e03b9d9e05090e *id_dsa 7e710598aa9ca70820280bae94eb287c *id_dsa.pub 57d104828a276ce86596d430bdb04c3f *known_hosts afcf3de480740f114659e87fcbb52470 *tbirdbld_dsa bd4d99a0082c92b67c313499b6d7e21c *tbirdbld_dsa.pub 2f51dc98ab1ed06da9b4b42c46349e24 *xrbld_dsa b788c4f3461101545fcc827248bdc8b4 *xrbld_dsa.pub Not sure who set these up, but this is really important to fix.
Reporter | ||
Comment 1•12 years ago
|
||
w64-ix-slave83 seems to have the right keys, not sure how that correlates with different batches.
Updated•12 years ago
|
Blocks: b-2008-ix-0096
Reporter | ||
Comment 2•12 years ago
|
||
Armen points out that this slave could've been set-up wrongly after coming back from loan. The history in https://bugzilla.mozilla.org/show_bug.cgi?id=w64-ix-slave79 supports this theory.
Comment 3•12 years ago
|
||
Disabled w64-ix-slave79 in slavealloc to staunch the bleeding while I can dig into it.
Comment 4•12 years ago
|
||
Has it ever been allocated to staging? Given the low number of win64 dev slaves, and general overcapacity, it's possible this was used in staging and not fixed up/re-imaged before being put back into production. My kingdom for slavealloc history.
Comment 5•11 years ago
|
||
What is left on this bug?
Comment 6•11 years ago
|
||
w64-ix-slave79 has the correct keys and has been put back into production. [1] https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•