Bug 35500

Summary: UCS in Active Directory domain & S4 Connector
Product: UCS Reporter: Arvid Requate <requate>
Component: S4 ConnectorAssignee: Arvid Requate <requate>
Status: CLOSED FIXED QA Contact: Felix Botner <botner>
Severity: enhancement    
Priority: P5 CC: gohmann, walkenhorst
Version: UCS 3.2   
Target Milestone: UCS 3.2-2-errata   
Hardware: Other   
OS: Linux   
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:
Bug Depends on: 35252    
Bug Blocks: 34091    

Description Arvid Requate univentionstaff 2014-07-28 18:08:54 CEST
In case univention-s4-connector gets installed in a domain configured for AD member mode the joinscript should configure connector/s4/autostart=no and abort.

+++ This bug was initially created as a clone of Bug #35252 +++
Comment 1 Arvid Requate univentionstaff 2014-07-28 18:36:17 CEST
The package has been adjusted and built in scope errata3.2-2.

Advisory: 2014-07-28-univention-s4-connector.yaml
Comment 2 Felix Botner univentionstaff 2014-08-01 09:58:01 CEST
OK 

timeout: finish: univention-directory-listener: (pid 18835) 10s, normally down
done.
Calling joinscript 97univention-s4-connector.inst ...
ERROR: The domain is in AD Member Mode.
Stopping univention-s4-connector daemon.
failed.
Create connector/s4/autostart
Create connector/s4/listener/disabled
sv status returns no running listener, don't need to restart..
Joinscript 97univention-s4-connector.inst finished with exitcode 1
Stopping univention-s4-connector daemon.
failed.
s4-connector disabled by ucr var connector/s4/autostart=no


OK - YAML
Comment 3 Janek Walkenhorst univentionstaff 2014-08-07 17:49:24 CEST
http://errata.univention.de/ucs/3.2/174.html