Closed
Bug 1080514
Opened 11 years ago
Closed 11 years ago
Reactivate commit access for fbraun@mozilla.com
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: freddy, Assigned: afernandez)
Details
Attachments
(3 files)
I can't seem to login anymore.
I get the same problem as https://bugzilla.mozilla.org/show_bug.cgi?id=580813#c10 had, which seems to be a server problem.
I am attaching a verbose log output as well as my ssh config to this bug.
| Reporter | ||
Comment 1•11 years ago
|
||
When is the last time you pushed? Your access may have expired.
| Reporter | ||
Comment 3•11 years ago
|
||
Oh yeah, that's very likely. I haven't pushed in a long while.
Assignee: mozillamarcia.knous → server-ops
Component: Repository Account Requests → Server Operations
QA Contact: shyam
Summary: commit access level 1 broken for fbraun@mozilla.com → Reactivate commit access for fbraun@mozilla.com
Comment 4•11 years ago
|
||
your hg access is still valid. I forced your ssh_key to re-sync. Hopefully this helps.
Assignee: server-ops → rbryce
| Reporter | ||
Comment 5•11 years ago
|
||
I still get the same thing as in sshlog.txt attached earlier
| Reporter | ||
Comment 6•11 years ago
|
||
For reference, I am attaching my ssh public key. It did not change.
| Reporter | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 7•11 years ago
|
||
Oct 10 00:55:41 hgssh1.dmz.scl3.mozilla.com sshd[12166]: Failed publickey for fbraun@mozilla.com from 10.22.74.212 port 35808 ssh2
The public key you had on file, was indeed different from the one you had on file.
I updated it with the one on comment 6.
Please allow sometime (~40mins or so) for the changes to take full effect.
Assignee: rbryce → afernandez
Comment 8•11 years ago
|
||
Assuming from the lack of comment that this is working, Please Reopen if not.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•