Univention Bugzilla – Bug 40045
80_docker/65_app_container_upgrade_dockerallowedimage test case fails
Last modified: 2023-03-25 06:46:56 CET
The test case fails on all 4.1 roles: For example: http://jenkins.knut.univention.de:8080/job/UCS-4.1/job/UCS-4.1-0/job/Autotest%20MultiEnv/SambaVersion=s3,Systemrolle=master/116/testReport/80_docker/65_app_container_upgrade_dockerallowedimage/test/ (2015-11-19 22:55:58.133293)dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p (2015-11-19 22:56:00.397597) dpkg-genchanges -b >../wvy6cedcin_2.1.0.3_amd64.changes (2015-11-19 22:56:01.053791)dpkg-genchanges: rein binärer Upload - es ist kein Quellcode hinzugefügt (2015-11-19 22:56:01.067242) dpkg-source --after-build wvy6cedcin (2015-11-19 23:04:34.066805)The connection to the repository server failed: Configuration error: host is unresolvable. Please check the repository configuration and the network connection. (2015-11-19 23:04:34.342293)Release upgrade script failed (2015-11-19 23:04:34.342321)Aborting... (2015-11-19 23:04:40.500917)sh: 0: getcwd() failed: No such file or directory (2015-11-19 23:04:41.834261)sh: 0: getcwd() failed: No such file or directory (2015-11-19 23:04:42.965774)sh: 0: getcwd() failed: No such file or directory (2015-11-19 23:04:44.632326)sh: 0: getcwd() failed: No such file or directory (2015-11-19 23:04:45.801540)sh: 0: getcwd() failed: No such file or directory (2015-11-19 23:04:46.909183)Traceback (most recent call last): (2015-11-19 23:04:46.909241) File "65_app_container_upgrade_dockerallowedimage", line 73, in <module> (2015-11-19 23:04:46.909319) app.upgrade() (2015-11-19 23:04:46.909357) File "/usr/share/ucs-test/80_docker/dockertest.py", line 166, in upgrade (2015-11-19 23:04:46.923197) raise UCSTest_DockerApp_UpgradeFailed() (2015-11-19 23:04:46.923220)dockertest.UCSTest_DockerApp_UpgradeFailed
The release upgrade in the docker container failed: Starting univention-upgrade. Current UCS version is 4.0-4 errata375 Checking for local repository: none Checking for release updates: found: UCS 4.1-0 Starting update to UCS version 4.1-0 HINT: Please check the release notes carefully BEFORE updating to UCS 4.1-0: English version: https://docs.software-univention.de/release-notes-4.1-0-en.html German version: https://docs.software-univention.de/release-notes-4.1-0-de.html Please also consider documents of following release updates and 3rd party components. Checking for space on /var/cache/apt/archives: OK Checking for space on /boot: OK Checking for space on /: OK Checking for package status: OK Starting update process, this may take a while. Check /var/log/univention/updater.log for more information. Running postup.sh script:done. Traceback (most recent call last): File "/usr/sbin/univention-upgrade", line 490, in <module> update_status(status='DONE') File "/usr/sbin/univention-upgrade", line 469, in main if options.iso: File "/usr/sbin/univention-upgrade", line 220, in performUpdate File "/usr/lib/pymodules/python2.7/univention/updater/tools.py", line 633, in ucr_reinit if not self.online_repository: File "/usr/lib/pymodules/python2.7/univention/updater/tools.py", line 492, in access self.log.exception("Failed %s %s: %s", req.get_method(), req.get_full_url(), ex) univention.updater.errors.ConfigurationError: Configuration error: host is unresolvable Release upgrade script failed Aborting... I had a ping running during the whole time to the repository server without any problems. After the exception, I could start univention-upgrade without any problems.
It works if I start univention-upgrade twice: ----------------------------------------------------------------------------- Starting univention-upgrade. Current UCS version is 4.0-4 errata377 Checking for local repository: none Checking for release updates: found: UCS 4.1-0 Starting update to UCS version 4.1-0 HINT: Please check the release notes carefully BEFORE updating to UCS 4.1-0: English version: https://docs.software-univention.de/release-notes-4.1-0-en.html German version: https://docs.software-univention.de/release-notes-4.1-0-de.html Please also consider documents of following release updates and 3rd party components. Checking for space on /var/cache/apt/archives: OK Checking for space on /boot: OK Checking for space on /: OK Checking for package status: OK Starting update process, this may take a while. Check /var/log/univention/updater.log for more information. Running postup.sh script:done. The connection to the repository server failed: Configuration error: host is unresolvable. Please check the repository configuration and the network connection. Starting univention-upgrade. Current UCS version is 4.1-0 errata0 Checking for local repository: none Checking for release updates: none Checking for package updates: found The following packages will be installed: dictionaries-common,sudo,univention-sudo,wngerman The following packages will be upgraded: libc-bin,libc6,libwbclient0,libtalloc2,python-ldb,python-tdb,libtdb1,libtevent0,python-talloc,python-samba,samba-common-bin,smbclient,samba-common,libsmbclient,samba-libs,libldb1,ntpdate,multiarch-support,locales,rpcbind,apache2-mpm-prefork,apache2.2-common,apache2.2-bin,apache2-utils,nscd,univention-directory-manager-tools,python-univention-directory-manager,python-univention-directory-manager-cli,python-univention-appcenter,univention-apache,univention-appcenter,univention-directory-listener,univention-errata-level,univention-system-setup,univention-updater,univention-mail-postfix,univention-pam Starting package upgrade done Checking for app updates: none Checking for release updates: none Checking for package updates: none ----------------------------------------------------------------------------- So, I think the first step should be to make univention-upgrade more fault tolerant. The upgrade was successful. I'll clone this issue to univention-upgrade where we should fix the univention-upgrade issue.
I've disabled the test case: r40338. It will be re-enabled after Bug #40338 was fixed. *** This bug has been marked as a duplicate of bug 40338 ***
For this bug is no separate QA needed.