Univention Bugzilla – Bug 47260
docker/autostart value changes are not recognized if they are changed on different layers
Last modified: 2018-07-04 15:29:55 CEST
A backport is needed for Bug #46300 The ucr autostart module is not scope aware. It uses the changed variable which it gets from ucr. That variable does not contain the effective change but only the change on the scope. [4.3-1 628afa8c38] Bug #46300: Do not ignore ucr layers in ucr autostart module +++ This bug was initially created as a clone of Bug #46300 +++
[4.2-4 4d37f9c2db] Bug #47260: Do not ignore ucr layers in ucr autostart module [4.2-4 6df9d1ea70] Bug #47260: YAML [4.2-4 7afa32b067] Bug #47260: yaml (version)
(In reply to Jürn Brodersen from comment #1) > [4.2-4 4d37f9c2db] Bug #47260: Do not ignore ucr layers in ucr autostart > module > [4.2-4 6df9d1ea70] Bug #47260: YAML > [4.2-4 7afa32b067] Bug #47260: yaml (version) OK. FYI: The customer is still using UCS_4.2-3, but we cannot announce the package for both UCS-4.2-3 and UCS-4.2-4 as the later already received an update and has diverged: <http://xen1.knut.univention.de:8000/packages/source/univention-base-files/?since=4.2-0&before=4.3-0> OK: apt install univention-base-files univention-base-packages OK: find /???/systemd -name docker.service -ls ucr set --ldap-policy docker/autostart=yes ucr set docker/autostart=no find /???/systemd -name docker.service -ls ucr unset --ldap-policy docker/autostart find /???/systemd -name docker.service -ls ucr set --forced docker/autostart=yes find /???/systemd -name docker.service -ls ucr unset --forced docker/autostart find /???/systemd -name docker.service -ls ucr set docker/autostart=yes find /???/systemd -name docker.service -ls OK: errata-announce -V --only univention-base-files.yaml OK: univention-base-files.yaml
<http://errata.software-univention.de/ucs/4.2/424.html>