|
Bugzilla – Full Text Bug Listing |
| Summary: | After zypper up and reboot Both zypper and yast report look up error | ||
|---|---|---|---|
| Product: | [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 | Reporter: | Bryan Kelley <aafa760> |
| Component: | zypper | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aafa760, dmueller, gpoppino, meissner |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Other | ||
| See Also: | https://bugzilla.opensuse.org/show_bug.cgi?id=1227741 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast screen shot
save_y2logs |
||
Created attachment 874508 [details]
save_y2logs
Logs files from yast error
See bug 1221119 comment #2 for a general explanation: > The root cause is incomplete execution of transactions while changing shared > library dependencies of zypper. > [...] > Bit of a systematic problem in how zypper executes rpm transactions (it does > not), but works fine in the absence of an interrupted upgrade. Also see https://build.opensuse.org/request/show/1169729 for work being done. @Dirk, may this be related to your work (https://build.opensuse.org/request/show/1169729)? If 'zypper up' was successfull, then the (auto)dependencies are broken. > 2024-04-25 06:10:00|command|root@sles15sp6-b1|'/usr/bin/ruby.ruby2.5' '--encoding=utf-8' '/usr/lib/YaST2/bin/y2start' 'installation' '--arg' 'initial' 'qt' '--noborder' '--auto-fonts' '--fullscreen'|
> 2024-04-25 06:11:18|install|libprotobuf-c1|1.5.0-150600.1.1|x86_64||Basesystem-Module_15.6-0|a1ed91b4b4a1af5a5ef76a61bdc81453766a629679e83cb370e82247d3b4ee2a|
> 2024-04-25 06:16:29|install|libprotobuf25_1_0|25.1-150400.9.3.1|x86_64||Basesystem-Module_15.6-0|36b99e61843d5158bd1648cecc62bf704c31effb6f63fb8e4e0617d7ef2a9819|
> 2024-04-25 06:16:30|install|libprotobuf-lite25_1_0|25.1-150400.9.3.1|x86_64||Basesystem-Module_15.6-0|99accaea3c59a4a07bffda5e37a3c4707d3f1569410b652dc80312dc90888640|
> 2024-04-25 06:22:56|install|libzypp|17.31.31-150600.8.2|x86_64||Basesystem-Module_15.6-0|e1f7d3fe70479029784a529fd6fcce8fc64e3de2fdd004edc0a2158289e5ab4d|
> 2024-04-25 06:26:25|install|abseil-cpp|20211102.0-150300.7.6.1|x86_64||SLEWE15-SP6_15.6-0|b65bb56f287ebdfbd36ff65d53195cf2b059a6f44d98abc9014f4a76d1a6483b|
> 2024-04-25 06:34:14|install|libzypp-plugin-appdata|1.0.1+git.20230117-150500.1.2|noarch||Desktop-Applications-Module_15.6-0|244f9d5a6fe427bff43e6363b3ee54a46eb2c87c15409f3363c18f612193d5dd|
>
> 2024-04-25 07:21:06|command|root@sles15sp6-b1|'zypper' 'up'|
> 2024-04-25 07:22:03|install|libprotobuf-c1|1.5.0-150600.1.3|x86_64||Basesystem_Module_15_SP6_x86_64:SLE-Module-Basesystem15-SP6-Pool|ffb075f74e6b48cbf27840eadd47506836e767ff4d0838221514304519f52d61|
> 2024-04-25 07:29:00|install|libzypp|17.31.31-150600.8.7|x86_64||Basesystem_Module_15_SP6_x86_64:SLE-Module-Basesystem15-SP6-Pool|d7a96326ef0f2fd1375c6c01eb5c51870d35bde64b3a249362bb7b9563c5473b|
> 2024-04-25 07:32:18|install|libzypp-plugin-appdata|1.0.1+git.20240209-150600.1.1|noarch||Desktop_Applications_Module_15_SP6_x86_64:SLE-Module-Desktop-Applications15-SP6-Pool|80afed61c056aaf12837772b99add4ab12e2dedd9a03580754c8d22f36ddab2e|
no, this is due to a weird mix of SP5 abseil libraries with SP4 protobuf built aghainst an older abseil. the publicrc should have fix this. Thanks Marcus. Closing it. Bryan, please reopen it if you experience similar with the publicRC. |
Created attachment 874507 [details] yast screen shot after install from SLE-15-SP6-Full-x86_64-PublicBeta-202403-Media1.iso and a successful zypper up The system reports the following error when entering zypper lu /code les15sp6-b1:~> zypper lu zypper: symbol lookup error: /usr/lib64/libzypp.so.1722: undefined symbol: _ZN6google8protobuf11MessageLite15ParseFromStringEN4absl12lts_2024011611string_viewE code/ will attached save_y2logs