Univention Bugzilla – Bug 44048
"domain" portal is used on DC slave after update
Last modified: 2017-04-04 18:30:07 CEST
A DC slave has been updated to 4.2. Afterwards, the computers object did have an empty entry for portal: > root@master:~# udm computers/domaincontroller_slave list | grep -e DN: -e portal: > DN: cn=slave,cn=dc,cn=computers,dc=w2k12,dc=test > portal: None However, the given portal was the domain portal: > python -c ' > import json > d=json.load(open("/var/www/univention/portal/portal.json")) > print d["portal"]["dn"]' > cn=domain,cn=portal,cn=univention,dc=w2k12,dc=test
The corresponding 35univention-portal join script had not been executed on the slave. I changed the fallback to the "local" portal to avoid problems like this on systems with pending join scripts. univention-portal (1.0.10-6): r78215 | Bug #44048: Use the local portal as fallback
OK, it works.
As discussed, the UMC link is only available after running the join scripts.
Fixed. Both portal objects as well as both UMC portal entries are now created in the join script for the role DC master. This should do the trick. In addition, I adjusted the server overview entry to be created (via the join script) on roles != DC master. That prevents one from having a link to the server overview on a single server domain. univention-portal (1.0.10-9): r78244 | Bug #44048: Create all portal objects at once on DC master univention-server-overview (0.0.3-8): r78245 | Bug #44048: Only create portal entry in a multi-sever domain
OK, it works now in a new installed domain and on an updated domain.
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".