Bug 45111

Summary: Don't re-provision if univention-samba4 gets uninstalled and re-installed
Product: UCS Reporter: Arvid Requate <requate>
Component: Samba4Assignee: Arvid Requate <requate>
Status: CLOSED FIXED QA Contact: Felix Botner <botner>
Severity: normal    
Priority: P5 Flags: requate: Patch_Available+
Version: UCS 4.1   
Target Milestone: UCS 4.1-4-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: Bug Report What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 1: Will affect a very few installed domains How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.200 Enterprise Customer affected?: Yes
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: 2017073121000288 Bug group (optional):
Max CVSS v3 score:
Bug Depends on: 44787    
Bug Blocks: 45126    

Description Arvid Requate univentionstaff 2017-08-01 14:14:09 CEST
We should backport this to UCS 4.1-4 too and check the special case of S4C hosted on a DC Backup.



+++ This bug was initially created as a clone of Bug #44787 +++
Comment 1 Arvid Requate univentionstaff 2017-08-01 21:07:45 CEST
Patches backported. I had to backport the univention-samba4 parts of Bug 43478 too.

Now, when I have the S4-Connector on a DC Backup (only) I can uninstall univention-samba4 and reinstall univention-s4-connector and everything continues to work, so we got Bug 44787 covered.


But to cover the situation of Ticket #2017073121000288 we need to do one additional thing: It should also work for re-joins, but in that case samba needs to be informed about the new machine.secret. I guess we should split that into a separate Bug, to be able to fix that transparently in errata4.2-1 and errata4.1-4

Advisory: univention-samba4.yaml
Comment 2 Felix Botner univentionstaff 2017-08-15 14:02:58 CEST
OK - update
OK - master (samba, connector), backup (samba)
   - master remove/install u-samba4 -> INFO: This system runs the 
      S4-Connector and the sam.ldb looks functional, 
      skipping re-provision.
   - backup remove/install u-samba4 -> dom join
OK - master (samba), backup (samba, connector), slave (samba)
   - master remove/install u-samba4 -> dom join
   - slave remove/install u-samba4 -> dom join
   - backup remove/install u-samba4 -> INFO: This system runs the 
      S4-Connector and the sam.ldb looks functional, 
      skipping re-provision.
OK - YAML
Comment 3 Erik Damrose univentionstaff 2017-08-16 13:34:13 CEST
<http://errata.software-univention.de/ucs/4.1/448.html>