Open Bug 1283226 Opened 8 years ago Updated 4 months ago

Pash timeout when connecting to LDAP master

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Product:
Developer Services
Component:
Mercurial: hg.mozilla.org
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: gps, Unassigned)

Details

As part of deploying the new hgssh servers, I discovered that pash can time out when attempting to connect to the LDAP master as part of updating the hg last access attribute.

Since the LDAP master server is in a separate class of service from the read-only servers (the latter is already required to connect to hg.mozilla.org via SSH key lookup), I reckon we should gracefully fail when we can't connect to the LDAP master. We may already do this. I wouldn't be surprised if our timeout is really high or something.
This doesn't need to block deploying of the new hardware.

But we should add a timeout here so LDAP master downtime doesn't take down hg.mozilla.org SSH access with it.
Assignee: gps → nobody
No longer blocks: 1283185
Status: ASSIGNED → NEW
QA Contact: hwine → klibby
You need to log in before you can comment on or make changes to this bug.