Closed Bug 816397 Opened 12 years ago Closed 12 years ago

Auth-related errors in stage server-storage deployment

Categories

(Cloud Services :: Operations: Miscellaneous, task)

Product:
Cloud Services
Component:
Operations: Miscellaneous
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rfkelly, Unassigned)

Details

Some of the stage server-storage webheads seem to be have problems authenticating user accounts. On sync4.web I am seeing instances of: OperationalError: (OperationalError) no such table: users I believe this is due to busted config files shipped in the server-storage RPMs, as discussed in Bug 781029. They're supposed to be overwritten by the good config files from puppet, but are not in this case. On sync3.web I am seeing instances of: ldap.INVALID_CREDENTIALS({'info': '', 'desc': 'Invalid credentials'},) Which seem likely due to jlaz's recent LDAP credentials changes. Not sure why they would affect just this single webhead though. Both sync1.web and sync2.web appear to be in working order. Please check and repair the sync.conf files on sync3.web and sync4.web.
Puppet was disabled on sync3.web.scl2.stage and sync4.web.scl2.stage. It has been enabled, and a Puppet run has been completed. The sync.conf files have been updated.
Confirming I can now sync against stage, and the loadtest scripts run at very low load show no errors. Closing this out.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.