Closed
Bug 1263648
Opened 10 years ago
Closed 10 years ago
Re-enable hg commit access for bbouvier@mozilla.com
Categories
(Infrastructure & Operations :: MOC: Service Requests, task)
Infrastructure & Operations
MOC: Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bbouvier, Assigned: Usul)
Details
I am bit struggling with what's going on, so let me explain to be sure what I'm asking for makes sense:
- when I go to https://login.mozilla.com/ssh_keys_index, there's one empty line that I can't delete (when I click the "delete" button I get a 404).
- I've uploaded a new public SSH key, created a few minutes ago, which purpose will be to push only to hg.mozilla.org.
- I *think* that I was able to push with my contributor email (i.e. not @mozilla.com) SSH key so far. That would explain the "User" line below "hg.mozilla.org" in my .ssh/config, plus the fact that I've received a LDAP password notification email on my contributor email address.
- The new key I've created is associated with the moco email address, which seems to be inactive. When I try to push or SSH, I get this message: "Your mercurial account has been disabled due to inactivity."
What I would like, ideally, is that my hg commit email remain the same (contributor email address). But I think it's not tied to the email address in the RSA key I'm pushing with. So my question is: if all of the above makes sense, can you please re-enable the mercurial account of bbouvier@mozilla.com, with the same commit access that I have with my contributor email address? (benj@benj.me)
| Reporter | ||
Updated•10 years ago
|
Assignee: nobody → infra
Component: Mercurial: hg.mozilla.org → Infrastructure: LDAP
Product: Developer Services → Infrastructure & Operations
QA Contact: hwine
| Assignee | ||
Comment 1•10 years ago
|
||
So you hg was disabled on your @moco email. re-enabled. but your moco doesn't have any scm levels so you won't be able to push.
Hg is enabled adn has all the rights you need on your contributor ldap.
I can't currently grant level3 access so I can add stuff to your @moco one (just level2).
jeff can you wave the level3 bit here ?
Flags: needinfo?(jbryner)
Comment 2•10 years ago
|
||
That's currently a DougT question
Flags: needinfo?(jbryner) → needinfo?(dougt)
| Reporter | ||
Comment 3•10 years ago
|
||
OK, confirmed that I could push with my contributor address benj@benj.me, now it's been invalidated, so I can't push on inbound anymore. Can somebody let me know what do I need to do to get commit rights back, please?
| Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(dougt)
| Assignee | ||
Updated•10 years ago
|
Assignee: infra → ludovic
Component: Infrastructure: LDAP → MOC: Service Requests
QA Contact: lypulong
| Assignee | ||
Comment 4•10 years ago
|
||
added level3 to the @moco account.
and did a reset password on the community account.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•