Bugzilla – Bug 1212090
Bind update in SUSE:Maintenance:28886 / [Build 20230606-1] openQA test fails in yast_dns_server due to libuv version
Last modified: 2024-03-12 16:10:18 UTC
Created attachment 867428 [details] coredump The yast_dns_module attempts to run the command: #dig www.opensuse.org +short The the system dumps core and the SUT produces the following error: fatal error: libuv version too new: running with libuv 1.44.2 when compiled with libuv 1.18.0 will lead to libuv failures the coredump files can be found attached and here: https://openqa.suse.de/tests/11269435#downloads ## Observation openQA test in scenario sle-15-SP5-Server-DVD-Updates-x86_64-mau_extratests_yast_cmd@64bit fails in [yast_dns_server](https://openqa.suse.de/tests/11269435/modules/yast_dns_server/steps/16) ## Test suite description Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Run console tests against aggregated test repo ## Reproducible Fails since (at least) Build [20230606-1](https://openqa.suse.de/tests/11267614) ## Expected result Last good: [20230605-1](https://openqa.suse.de/tests/11263117) (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=mau_extratests_yast_cmd&version=15-SP5)
this is caused by the bind version update. SUSE:Maintenance:28886/bind.SUSE_SLE-15-SP4_Update libuv on SLES 15 SP4 is used for building (1.18.0) and the bind is used for both SLES 15 Sp4 and SP5. SP4 has libuv 1.18.0 SP5 has libuv 1.44.2 Options: - update SP4 libuv to same as SP5 - fork bind into SP5 so it is built against and uses libuv 1.44.2.
*** Bug 1212093 has been marked as a duplicate of this bug. ***
(In reply to Marcus Meissner from comment #1) > Options: > > - update SP4 libuv to same as SP5 > - fork bind into SP5 so it is built against and uses libuv 1.44.2. I think forking bind into SP5 is the better option. Since I'm not that familiar yet with the processes, what do I need to do here?
Forking is done by maintenance team, you should submit your changes separately to SP5 then.
i have done this with the current security update.
This is an autogenerated message for OBS integration: This bug (1212090) was mentioned in https://build.opensuse.org/request/show/1097046 Factory / bind https://build.opensuse.org/request/show/1097048 Factory / cmake
SUSE-SU-2023:2836-1: An update that solves two vulnerabilities, contains one feature and has one fix can now be installed. Category: security (important) Bug References: 1212090, 1212544, 1212567 CVE References: CVE-2023-2828, CVE-2023-2911 Jira References: SLE-24600 Sources used: openSUSE Leap 15.5 (src): bind-9.16.42-150500.8.3.1 Basesystem Module 15-SP5 (src): bind-9.16.42-150500.8.3.1 Server Applications Module 15-SP5 (src): bind-9.16.42-150500.8.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.