Bugzilla – Bug 1212136
yast2-pkg-bindings update is breaking installer
Last modified: 2023-06-21 07:19:07 UTC
Created attachment 867451 [details] y2logs yast2-pkg-bindings update https://build.suse.de/request/show/300770 is breaking installer with or without autoyast https://openqa.suse.de/tests/11275975/modules/installation/steps/3
Once again, there is NO hint what that OpenQA test does. There is no hint what you were trying to do. Again, we have to rely on guesswork. I see a sequence of screenshots that might be ANYTHING. You don't even bother to tell us your test scenario. Please read https://en.opensuse.org/openSUSE:How_to_Write_a_Good_Bugreport
y2start.log says Stage [call]: ============================ Stage [call]: Check selected medium... Stage [call]: ======================== |-- Wished medium is: QT |-- Selected medium is: QT |-- X-Server is ready: 3867 |-- Allow big memory allocation: overcommit_memory=1 |-- Starting YaST2: |-- MODULE_NAME: installation |-- MODE_FLAGS: |-- MODULE_ARGS: --arg initial |-- MODE: qt |-- UI_ARGS: --noborder --auto-fonts --fullscreen |-- QT_IM_MODULE: xim |-- Y2_EXIT_CODE: 0 |-- Allow big memory allocation: overcommit_memory=1 |-- Starting YaST2: |-- MODULE_NAME: installation |-- MODE_FLAGS: |-- MODULE_ARGS: --arg initial |-- MODE: qt |-- UI_ARGS: --noborder --auto-fonts --fullscreen |-- QT_IM_MODULE: xim |-- Y2_EXIT_CODE: 127 |-- Reset memory allocation: overcommit_memory=1 |-- Reset memory allocation: overcommit_memory=0 |-- Copy first level log file to installed system |-- Creating hook script list: postFirstCall... Stage [1]: Starting F10-cleanup... Stage [1]: ======================= |-- YaST2 exit code on level (1): 127 |-- Stopping UTF-8 mode... |-- Creating hook script list: postFirstStage...
There is no backtrace in the y2logs. It ends abruptly with: > 2023-06-07 22:04:29 <1> install(13159) [zypp] MediaHandler.cc(createAttachPoint):373 Created default attach point /var/adm/mount/AP_0xxGSXBd > 2023-06-07 22:04:29 <1> install(13159) [zypp::exec++] ExternalProgram.cc(start_program):260 Executing[C] '/bin/mount' '-t' 'iso9660' '-o' 'ro' '/dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0' '/var/adm/mount/AP_0xxGSXBd' > 2023-06-07 22:04:29 <1> install(13159) [zypp::exec++] ExternalProgram.cc(start_program):444 pid 13223 launched > 2023-06-07 22:04:29 <1> install(13159) [zypp::exec++] ExternalProgram.cc(checkStatus):549 Pid 13223 successfully completed > 2023-06-07 22:04:29 <1> install(13159) [zypp++] Mount.cc(Status):263 exit code: 0 > 2023-06-07 22:04:29 <1> install(13159) [zypp] Mount.cc(mount):159 mounted /dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0 /var/adm/mount/AP_0xxGSXBd > 2023-06-07 22:04:29 <1> install(13159) [zypp++] MediaHandler.cc(checkAttached):528 Forced check of the mount table > 2023-06-07 22:04:29 <1> install(13159) [zypp++] MediaHandler.cc(checkAttached):552 Found media device cdrom</dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0[11,0]> in the mount table as /dev/sr0 > 2023-06-07 22:04:29 <1> install(13159) [zypp++] MediaCD.cc(attachTo):533 0 1 > 2023-06-07 22:04:29 <1> install(13159) [zypp] Mount.cc(~Mount):57 ~Mount() > 2023-06-07 22:04:29 <1> install(13159) [zypp] Mount.cc(~Mount):64 ~Mount() end > 2023-06-07 22:04:29 <1> install(13159) [zypp] MediaHandler.cc(attach):690 Attached: cd:/?devices=/dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0 attached; localRoot "/var/adm/mount/AP_0xxGSXBd" > 2023-06-07 22:04:29 <1> install(13159) [zypp++] MediaManager.cc(checkDesired):96 checkDesired(1): desired (report by zypp::media::NoVerifier)
What makes you so sure that a yast2-pkg-bindings update causes this? Did you try with debug logging since there is no hint what's happening?
(In reply to Stefan Hundhammer from comment #4) > Did you try with debug logging since there is no hint what's happening? Disregard; I just saw log level <0> (debug) in the y2log.
Sorry Stefan, it's any installation run with self_update=http://download.suse.de/ibs/SUSE:/Maintenance:/29292/SUSE_SLE-15-SP3_Update/, installation will crash after self update
Created attachment 867466 [details] console before installation crashes and returns to linuxrc
(In reply to Jozef Pupava from comment #6) > Sorry Stefan, it's any installation run with > self_update=http://download.suse.de/ibs/SUSE:/Maintenance:/29292/SUSE_SLE-15- > SP3_Update/, installation will crash after self update That repository misses the libzypp package. My guess is that yast2-pkg-bindings was built against the updated libzypp but after applying the self-update it loads original SP3 libzypp from medium which is not compatible and this causes the crash. Could you try adding the latest libzypp to that repository?
This recent PR (from 2 weeks ago) https://github.com/yast/yast-pkg-bindings/pull/174 updates yast-pkg-bindings from version 4.3.11 from SLE-15-SP3:GA from 2 years ago with version 4.3.12. https://build.suse.de/package/show/SUSE:SLE-15-SP3:Update/yast2-pkg-bindings libzypp OTOH received several updates; SLE-15-SP3:Update inherits it from SLE-15-SP2:Update. Currently, we are at libzypp-17.31.11 from 1 month ago. https://build.suse.de/package/show/SUSE:SLE-15-SP3:Update/libzypp Maybe there is a problem in the build process for that maintenance request. When I look at that pull request from above, I don't see what yast-pkg-bindings could possibly do wrong here.
The self-update installed those packages: > 2023-06-07 22:04:12 <1> install(3930) [zypp] > PackageProvider.cc(providePackage):513 > provided Package ... > (3) augeas-1.10.1-150000.3.12.1.x86_64 > (8) augeas-lenses-1.10.1-150000.3.12.1.x86_64 > (16) autoyast2-4.3.106-150300.3.55.1.noarch > (29) autoyast2-installation-4.3.106-150300.3.55.1.noarch > (39) libaugeas0-1.10.1-150000.3.12.1.x86_64 > (43) libstdc++6-12.3.0+git1204-150000.1.10.1.x86_64 > (62) release-notes-sles-15.3.20230301-150300.3.32.1.noarch > (75) yast2-4.3.69-150300.3.20.1.x86_64 > (76) yast2-add-on-4.3.10-150300.3.8.1.noarch > (81) yast2-bootloader-4.3.32-150300.3.11.1.x86_64 > (89) yast2-country-4.3.19-150300.3.14.1.x86_64 > (92) yast2-country-data-4.3.19-150300.3.14.1.x86_64 > (105) yast2-installation-4.3.55-150300.3.34.2.noarch > (107) yast2-iscsi-client-4.3.4-3.3.2.noarch > (115) yast2-network-4.3.86-150300.3.35.1.noarch > (122) yast2-packager-4.3.26-150300.3.11.1.x86_64 > (124) yast2-pkg-bindings-4.3.12-150300.3.3.1.x86_64 > (125) yast2-proxy-4.3.3-3.5.1.noarch > (136) yast2-schema-4.3.31-150300.3.20.3.x86_64 > (142) yast2-storage-ng-4.3.60-150300.3.21.1.x86_64 Notice that there was no libzypp and no libsolv among them.
I don't see that this is a YaST problem. It looks more like a problem with that update / maintenance repo to me. Please try what Ladislav suggested in comment #8.
Thank you, I asked coordinator to add libzypp, I will update the bug when the release request is resubmitted.
See also bug #1212430: missing libzck. That may or may not be related.
If lslezak's https://build.suse.de/request/show/301410 fixed bsc#1212430, please check if the backport of that change to SLE-15-SP3 fixed this problem as well: https://build.suse.de/request/show/300032 This also requires a more recent yast2-pkg-bindings (>= 4.3.12) which will require a newer libzypp which might resolve this problem.
juraj has fixed this up i think. i branched in the SP2 yast2-pkg-bvindings as this otherwise will also cause problems on SP2 self nstaller.
OK, then let's close this for now. Please reopen if the problem reappears.