Univention Bugzilla – Bug 29885
VMware image with UCS 3.1-0-errata
Last modified: 2023-03-25 06:41:27 CET
A new VMware image should be created and released.
I updated the VMware image and put it temporarily on omar:/tmp/aklaeser. The image contains all current errata updates, univention-system-setup-boot has been reinstalled (in order to keep the local cached package versions up-to-date [QA: please double-check]), the UCR variable system/setup/boot/start has been set to "true", network settings have been reset after the update.
The image can be booted and does so into System setup (=> the UCR variable system/setup/boot/start has been set to "true"). Network page shows that DHCP is activated. Ctrl+q is possible. Every package that has seen at least one errata-update is up-to-date (last update: Today at 15:14). I double-checked installed versions of univention-system-setup{-boot} and python-univention-lib. As far as I can see, these are the most important packages for the image. I did not do any further testing as has been done during the Errata-QA.
(In reply to comment #2) > Every package that has seen at least one errata-update is up-to-date (last > update: Today at 15:14). I double-checked installed versions of > univention-system-setup{-boot} and python-univention-lib. As far as I can see, > these are the most important packages for the image. > > I did not do any further testing as has been done during the Errata-QA. I think the following things should be tested: - configure the image to a master and join a windows client into the S4 domain - install some applications from the app center - configure a master + backup, slave, member and join them
I had problems joining a Windows machine -> Bug#30044 REOPENED, until the issue is resolved. Maybe it is even necessary to rebuild the image.
See http://wiki.univention.de/index.php?title=UCS_Appliance#Preparing_VMware_Images, I think these files should be removed: inflating: UCS 3.1-0/vmware.log inflating: UCS 3.1-0/nvram I can reproduce the S4 connector issue if I change the IP address. The following lines should be executed and added to the wiki article: # Ensure s4connector will be restated after the configuration cat >/usr/lib/univention-system-setup/appliance-hooks.d/s4connector <<__EOF__ #!/bin/sh test -x /etc/init.d/univention-s4-connector && /etc/init.d/univention-s4-connector restart __EOF__ chmod +x /usr/lib/univention-system-setup/appliance-hooks.d/s4connector
(In reply to comment #5) > See > http://wiki.univention.de/index.php?title=UCS_Appliance#Preparing_VMware_Images, > I think these files should be removed: > > inflating: UCS 3.1-0/vmware.log > inflating: UCS 3.1-0/nvram > > I can reproduce the S4 connector issue if I change the IP address. The > following lines should be executed and added to the wiki article: > ... Could this also affect the EC2 images (Bug 29886)? I adapted the Wiki page, added the s4connector appliance hook and removed log and nvram file. I updated the image in /tmp/aklaeser
The issue remains unfixed. The script is present, but the connector is still not working out-of-the-box (i.e. has to be restarted manually).
(In reply to comment #7) > The issue remains unfixed. The script is present, but the connector is still > not working out-of-the-box (i.e. has to be restarted manually). This problem could be reproduced when setting up a master system and changing its IP address from DHCP to static. See also Bug 30119.
I prepared a new image → omar:/tmp/aklaeser
(In reply to comment #9) > I prepared a new image → omar:/tmp/aklaeser I still seem to have the same problem that should be fixed with Bug 30119. Adding a new user would not be replicated into Samba4. After a restart of the s4-connector everything seems to be ok.
The installed version of the s4-connector is 7.0.22-9.365.201301241501 → seems to be the correct one!
Can you test my images? I can't reproduce it with this image: stefan@leksvik:/$ ls /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip stefan@leksvik:/$ cat /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip.md5 93340dd53986847833fcf6c0e06d8e97 ucs-3.1-0errata37-demo-image.zip stefan@leksvik:/$
(In reply to comment #12) > Can you test my images? I can't reproduce it with this image: > > stefan@leksvik:/$ ls /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip > /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip > stefan@leksvik:/$ cat /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip.md5 > 93340dd53986847833fcf6c0e06d8e97 ucs-3.1-0errata37-demo-image.zip > stefan@leksvik:/$ Same problem → the listener needs a restart script in /etc/network/if-down.d (see also Bug 30408)
(In reply to comment #13) > (In reply to comment #12) > > Can you test my images? I can't reproduce it with this image: > > > > stefan@leksvik:/$ ls /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip > > /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip > > stefan@leksvik:/$ cat /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip.md5 > > 93340dd53986847833fcf6c0e06d8e97 ucs-3.1-0errata37-demo-image.zip > > stefan@leksvik:/$ > > Same problem → the listener needs a restart script in /etc/network/if-down.d > (see also Bug 30408) New image with a manual fix for Bug #30408 and Bug #30412: stefan@leksvik:/$ ls /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip stefan@leksvik:/$ cat /srv/vmware/stefan/ucs-3.1-0errata37-demo-image.zip.md5 49c24a66464bebab91d0308e34ba130e ucs-3.1-0errata37-demo-image.zip stefan@leksvik:/$
Now users are synced in both directions: UCS → S4 and S4 → UCS.