Bug 51618 - Add service restart option after policy based update
Add service restart option after policy based update
Status: NEEDMOREINFO
Product: UCS
Classification: Unclassified
Component: Update - Release updates
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-07-06 14:05 CEST by Christian Völker
Modified: 2020-09-09 13:42 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
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?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2020070321000691
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 Christian Völker univentionstaff 2020-07-06 14:05:30 CEST
Usually when updates are performed based on a policy schedule no services are restarted.

But this can cause issues i.e. for samba when trying to load modules at a later stage:
===================================
ldb: module version mismatch in ../../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.5.7 module_version=1.5.8
ldb: failed to initialise module /usr/lib/x86_64-linux-gnu/samba/ldb/acl.so : Unavailable
===================================

which causes a loss on Samba functionality and needs a manual restart of Samba.

I would suggest so add an option to the update policies to optionally restart affected services (as most of the time updates are scheduled for night time).
Comment 1 Erik Damrose univentionstaff 2020-07-06 14:18:10 CEST
Where did you see that error / in which context? The affected debian package should definitely restart services in the postinst if required.

(In reply to Christian Völker from comment #0)
> Usually when updates are performed based on a policy schedule no services
> are restarted.

I am not completely sure what you mean - if packages are updated, the postinst will be run, and services get restarted. There is nothing in UCS policies that prevents this