Bug 32529 - S4 connector does not get restarted if machine password (machine.secret) changes
S4 connector does not get restarted if machine password (machine.secret) changes
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 3.1
Other Linux
: P5 normal (vote)
: UCS 3.1-1-errata
Assigned To: Stefan Gohmann
Felix Botner
Depends on:
  Show dependency treegraph
Reported: 2013-09-09 12:23 CEST by Sönke Schwardt-Krummrich
Modified: 2013-10-07 14:44 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2013-09-09 12:23:23 CEST
Noticed on UCS@school slaves with samba4 connector:
if the slave had changed its machine password (machine.secret) the s4connector seems to use the old machine.secret for writes in OpenLDAP on the dc master. All write requests are rejected with "invalid credentials". After a restart of the
s4 connector, these problems disappear and the connector tries to catch up the failed objects.
Comment 1 Tim Petersen univentionstaff 2013-09-09 14:59:08 CEST
Also seen here: 2013090921002054
Comment 2 Stefan Gohmann univentionstaff 2013-09-25 06:58:42 CEST
Fixed. This is only relevant if you are using the s4 connector on a slaves, like in UCS@school.

Fix 3.1: r44378 + r44386
YAML 3.1: r44388
Fix 3.2: r44379
Changelog 3.2: r44382
Comment 3 Felix Botner univentionstaff 2013-09-25 16:39:12 CEST
OK - errata3.1-1

OK - ucs3.2-1
OK - Changelog
Comment 4 Moritz Muehlenhoff univentionstaff 2013-10-07 14:44:24 CEST