Bugzilla – Bug 1219950
SLES12-SP5 apache2 requires systemd
Last modified: 2024-02-21 10:48:55 UTC
Created attachment 872753 [details] `docker build .` output From 13th February the apache2 package requires systemd which breaks the SLES12-SP5 base container: > # cat Dockerfile > FROM registry.suse.com/suse/sles12sp5 > > RUN zypper -n in apache2 && zypper clean -a > RUN echo 'ServerName AppacheInContainer' >> /etc/apache2/httpd.conf > > WORKDIR /srv/www/htdocs/ > COPY index.html . > EXPOSE 5000 > ENTRYPOINT ["/usr/sbin/start_apache2", "-DFOREGROUND", "-k", "start"] > docker build . > … > (34/43) Installing: systemd-228-157.57.1.x86_64 [............done] > Additional rpm output: > Creating group systemd-journal with gid 498. > Creating group systemd-timesync with gid 497. > Creating user systemd-timesync (systemd Time Synchronization) with uid 497 and gid 497. > Initializing machine ID from D-Bus machine ID. > [/usr/lib/tmpfiles.d/dirmngr.conf:1] Line references path below legacy directory > /var/run/, updating /var/run/dirmngr → /run/dirmngr; please update the tmpfiles.d/ > drop-in file accordingly. > Created symlink from /etc/systemd/system/multi-user.target.wants/remote-fs.target to > /usr/lib/systemd/system/remote-fs.target. > Created symlink from /etc/systemd/system/getty.target.wants/getty@tty1.service to > /usr/lib/systemd/system/getty@.service. > (35/43) Installing: device-mapper-1.02.172-12.9.4.x86_64 [............done] > Additional rpm output: > Failed to connect to bus: No such file or directory I will upload the whole output separately. With best regards Pavel Dostál ## Observation openQA test in scenario sle-15-SP5-Server-DVD-Updates-x86_64-docker_cgroupv2_tests@64bit fails in [image_docker](https://openqa.suse.de/tests/13523162/modules/image_docker/steps/194) ## Test suite description The base test suite is used for job templates defined in YAML documents. It has no settings of its own. ## Reproducible Fails since (at least) Build [20240214-1](https://openqa.suse.de/tests/13522679) ## Expected result Last good: [20240213-1](https://openqa.suse.de/tests/13517608) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=docker_cgroupv2_tests&version=15-SP5)
last good is the same failure, but soft-failed
(In reply to Marcus Meissner from comment #1) > last good is the same failure, but soft-failed This is the real last good: https://openqa.suse.de/tests/13431819 The one recorded by the template was manually set to softfail
The culprit was that nvidia repo has a new key that the test code was not importing by default. ``` Retrieving repository 'SLE-12-SP5-GA-Desktop-nVidia-Driver' metadata [.. New repository or package signing key received: Repository: SLE-12-SP5-GA-Desktop-nVidia-Driver Key Name: NVIDIA Corporation <linux-bugs@nvidia.com> Key Fingerprint: 9B763D49 D8A5C892 FC178BAC F5113243 C66B6EAE Key Created: Thu Jun 15 16:13:18 2006 Key Expires: (does not expire) Subkey: F016EEAA03224CDD 2006-06-15 [does not expire] Rpm Name: gpg-pubkey-c66b6eae-4491871e Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): r error] Repository 'SLE-12-SP5-GA-Desktop-nVidia-Driver' is invalid. ``` This has been resolved, so I guess we can close this report.