Bugzilla – Bug 1220673
Two BCI failures with bci-base 15.6
Last modified: 2024-03-06 13:08:09 UTC
In the current 15-SP6 validation round we see two issues with the bci-base:156 container, e.g. in https://openqa.suse.de/tests/13634256 > AssertionError: Installed crypto-policies = 150600.1.8 is newer than what crypto-policies-scripts requires (= 150600.1.3) and > > assert not orphaned_packages.difference(known_orphaned_packages) > E AssertionError: assert not {'libabsl2308_0_0', 'libopenssl-3-fips-provider', 'libprotobuf-lite25_1_0', 'sle-module-basesystem-release', 'sle-module-python3-release', 'sle-module-server-applications-release'} > E + where {'libabsl2308_0_0', 'libopenssl-3-fips-provider', 'libprotobuf-lite25_1_0', 'sle-module-basesystem-release', 'sle-module-python3-release', 'sle-module-server-applications-release'} We're testing currently build 44.45.
first: needs repo refresh second: 000package-groups in SUSE:SLE-15-SP6:Update:BCI needs to updated for lib* to be included. the sle-*-release packages its not clear, nott sure where they come from or if they should be there
The repo refresh is blocked by the broken openssl3/fips state, there's a separate bug report about it
FWICT the image contains newer libabsl and protobuf from a SLE maintenance update, which implies that it was built against SUSE:SLE-15-SP6:Update instead of SUSE:15-SP6:GA. > the sle-*-release packages its not clear, nott sure where they come from or if they should be there Not sure. sle15:15.5 doesn't have those OOTB.
(In reply to Fabian Vogt from comment #3) > > the sle-*-release packages its not clear, nott sure where they come from or if they should be there > > Not sure. sle15:15.5 doesn't have those OOTB. .changes has the answer: ------------------------------------------------------------------- Thu Jan 25 11:45:28 UTC 2024 - Dirk Müller <dmueller@suse.com> - install the default modules (bsc#1219178) - add README.md and point to it for artifacthub
(In reply to Fabian Vogt from comment #3) > FWICT the image contains newer libabsl and protobuf from a SLE maintenance > update, which implies that it was built against SUSE:SLE-15-SP6:Update > instead of SUSE:15-SP6:GA. These are in SP6:GA too now after the last maintenance snapshot.
solved