Bug 43192 - Jenkins shows: ucs-school-webproxy update breaks winbind update (Samba3)
Jenkins shows: ucs-school-webproxy update breaks winbind update (Samba3)
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Proxy services
UCS@school 4.1 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-15 21:06 CET by Arvid Requate
Modified: 2019-02-05 21:43 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2016-12-15 21:06:34 CET
This bug has been split off from Bug 43144 Comment 9, because it is actually an UCS@school bug. See Bug 43144 Comment 9 for an introduction about the damage.

I was able to reproduce that in the Samba3 UCS@school singleserver Jenkins test, where the final update to the test-errata gives this:

===========================================================================
root@master205:~# dpkg -C
Die folgenden Pakete sind nur halb konfiguriert, wahrscheinlich durch
Probleme während der ersten Konfiguration. Die Konfiguration sollte mit
dpkg --configure <Paket> oder mit dem Konfigurations-Menüeintrag in
dselect erneut versucht werden:
 winbind              service to resolve user and group information from Window

root@master205:~# ps ax | grep winbind
 4065 ?        Ss     0:00 /usr/sbin/winbindd
 4085 ?        S      0:00 /usr/sbin/winbindd

root@master205:~# dpkg --configure winbind
winbind (2:4.5.1-1.849.201612142005) wird eingerichtet ...
[FAIL] Starting the Winbind daemon: winbind failed!
invoke-rc.d: initscript winbind, action "start" failed.
dpkg: Fehler beim Bearbeiten von winbind (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 winbind

root@master205:~# start-stop-daemon --start  --exec /usr/sbin/winbindd --
/usr/sbin/winbindd already running.
===========================================================================

The updater.log shows:
===========================================================================
Vorbereitung zum Ersetzen von winbind 2:4.5.1-1.848.201611070734 (durch .../winbind_2%3a4.5.1-1.849.201612142005_amd64.deb) ...
Stopping the Winbind daemon: winbind.
Ersatz für winbind wird entpackt ...
[...]
ucs-school-webproxy (12.0.4-2.124.201611231142) wird eingerichtet ...
[...]
Setting squid/acl/windowsupdater/allow/dstdomain-i/regex
File: /etc/squid3/squid.conf
Reloading /etc/samba/smb.conf: smbd onlyNo process in pidfile '/var/run/samba/smbd.pid' found running; none killed.
.
Stopping the Winbind daemon: winbind.
Starting the Winbind daemon: winbind.
Restarting Squid HTTP Proxy 3.x: squid3 Waiting.....................done.
.
Enabling site wpad-config.
[...]
winbind (2:4.5.1-1.849.201612142005) wird eingerichtet ...
Starting the Winbind daemon: winbind failed!
invoke-rc.d: initscript winbind, action "start" failed.
dpkg: Fehler beim Bearbeiten von winbind (--configure):
===========================================================================

So this is the ucs-school-webproxy.postinst restarting winbind between winbind.prerm where it was stopped and winbind.postinst where it fails to get started.

ucs-school-webproxy.postinst should use /etc/init.d/winbind crestart.
Unfortunately that init script doesn't offer that currently.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:43:41 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with
bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.