Univention Bugzilla – Bug 46847
dpkg-statoverride location change in UCS 4.3
Last modified: 2018-04-19 11:35:08 CEST
dpkg-statoverride has moved from /usr/sbin/dpkg-statoverride in UCS 4.2 to /usr/bin/dpkg-statoverride in UCS 4.3
This causes an interesting effect: With a UCS 4.3 UMC-server package erratum that is updated during system setup, no appliance hooks will be executed. The chain of events is
start system-setup, which calls setup-join.sh; this calls /usr/share/univention-updater/disable-apache2-umc to disable umc server restarts during setup. That script calls dpkg-statoverride (with full path!) to keep the executable bit removed from umc-server even with package updates
As the path changed in 4.3, the statoverride is never applied. So a new umc-server package that is updated during system-setup installs the binary with executeable bit. Now umc-server can be restarted by the packages postinst, which kills the setup-join.sh process, and setup-join.sh will not run completely.
This causes missing calls to running the appliance hooks, several ucr commit calls,..
e9f70471 Fix path to dpkg-statoverride in UCS 4.3
Fix path to executable in univention-updater
During system-setup, the umc-server binary now has wrong
permissions. That is fixed in the umc-server.poinst
d9ffd4ad + bb9c35fb revert untested commits from packages
QA Test: To reproduce: Use UCS 4.3 image with erratalevel less than 18, select 'update packages' in system setup. Symptom: No appliance hooks will be called; setup.log will not contain the line
"=== Running appliance hook scripts"
For testing the erratum: Add internal erata4.3-0 apt repo to sources.list manually before package updates are installed by system setup. Appliance hooks should be executed again
* Code review: Ok
* Functional A/B Test: Reproducible and fixed by this update
* Revert-Commit "bb9c35fb" Ok, inverse of 52e04b9d
* Advisories: Ok