Bug 30720 - DNF failed after mga8 update to Cauldron and initial reboot
Summary: DNF failed after mga8 update to Cauldron and initial reboot
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-07 05:07 CEST by Edward
Modified: 2022-08-10 22:18 CEST (History)
1 user (show)

See Also:
Source RPM: dnf-4.13.0-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Edward 2022-08-07 05:07:21 CEST
Description of problem:

Installed mga8 with MATE desktop in a VirtualBox and had some trouble updating it to Cauldron. Due to an issue with the math-princeton mirror (see qa-discuss ML), I could not initially update with urpmi. I was able to use dnf to partially update the system. After the first reboot, I realized I forgot to add the nonfree repo, so when I launched dnf to add it, dnf failed to work:

Traceback (most recent call last):
  File "/bin/dnf", line 57, in <module>
    from dnf.cli import main
  File "/usr/lib/python3.8/site-packages/dnf/__init__.py", line 30, in <module>
    import dnf.base
  File "/usr/lib/python3.8/site-packages/dnf/base.py", line 32, in <module>
    from dnf.comps import CompsQuery
  File "/usr/lib/python3.8/site-packages/dnf/comps.py", line 27, in <module>
    from dnf.exceptions import CompsError
  File "/usr/lib/python3.8/site-packages/dnf/exceptions.py", line 22, in <module>
    import dnf.util
  File "/usr/lib/python3.8/site-packages/dnf/util.py", line 29, in <module>
    import dnf.callback
  File "/usr/lib/python3.8/site-packages/dnf/callback.py", line 22, in <module>
    import dnf.yum.rpmtrans
  File "/usr/lib/python3.8/site-packages/dnf/yum/rpmtrans.py", line 26, in <module>
    import rpm
  File "/usr/lib64/python3.8/site-packages/rpm/__init__.py", line 38, in <module>
    from rpm._rpm import *
ImportError: /lib64/librpmbuild.so.9: undefined symbol: rpmlogGetNrecsByMask



Version-Release number of selected component (if applicable):

4.13.0-1



Additional information:

I was able to launch the MCC after this, added the repos from distrib-coffee and then used urpmi to update the remainder of the packages. I will continue to use urpmi for further updates to this install.

dnf launched successfully, after using urpmi to update the remainder of the packages. I do not know if this was a temporary problem with dnf, but wanted to submit this in any event.
Comment 1 Jani Välimaa 2022-08-07 12:21:45 CEST
Looks like at least your python3-rpm and dnf was still mga8 one. Did you use 'dnf system-upgrade'?

https://wiki.mageia.org/en/Using_DNF#Upgrade_Mageia_release_using_DNF
Comment 2 Edward 2022-08-07 15:15:49 CEST
No. I went by the instructions at https://wiki.mageia.org/en/Cauldron

The updater (mgaonline) did not launch this morning, so I had no idea if there were updates available. It is on the defaults to check every 3 hours and launch 5 minutes after login. I ran urpmi and there were several. I will be filing an enhancement bug report for mgaonline, which I believe will be an improvement to it.
Comment 3 Edward 2022-08-07 15:17:27 CEST
If mgaonline does not launch at next login or after three hours, I'll have to delete this VM and start over again.
Comment 4 sturmvogel 2022-08-07 15:25:53 CEST
In cauldron you have to use either urpmi update (or the dnf equivalent) or the way through MCC.
This was discussed already several times.
Comment 5 sturmvogel 2022-08-07 15:28:01 CEST
As in cauldron the updates won't go in the update repo but directly into the release repo, mgaonline doesn't work like at a normal Mageia release version.
Comment 6 Edward 2022-08-07 15:47:26 CEST
I have the Xfce desktop installed in a separate VirtualBox, also updated to Cauldron and mgaonline works perfectly. If it indicates updates are available, I use urpmi to update.
Comment 7 sturmvogel 2022-08-07 16:46:36 CEST
Forum search throws many hints as example:
https://forums.mageia.org/en/viewtopic.php?f=7&t=13572&p=79583&hilit=mgaonline#p79583
Comment 8 Jani Välimaa 2022-08-07 18:57:01 CEST
(In reply to Edward from comment #2)
> No. I went by the instructions at https://wiki.mageia.org/en/Cauldron
> 

I guess someone should update the wiki part to recommend to use 'dnf system-upgrade' to avoid partial updates causing issues like this.

https://wiki.mageia.org/en/Using_DNF#Upgrade_Mageia_release_using_DNF

CC: (none) => jani.valimaa

Comment 9 sturmvogel 2022-08-07 19:36:24 CEST
(In reply to Jani Välimaa from comment #8)
>someone should update the wiki 

done...
Comment 10 sturmvogel 2022-08-10 22:18:19 CEST
The initial problem from Edward was caused by the old wiki instruction to use only "dnf --refresh distro-sync".

According the hint from Jani i adapted the wiki to use the system-upgrade way (similar to https://wiki.mageia.org/en/Using_DNF#Upgrade_Mageia_release_using_DNF).

To verify that everything works as expected i did following test:

- created a MGA8 64bit Plasma VB and fully updated it
- cloned this VB

- one VB was updated to cauldron with the old instructions from wiki
-> result was an unusable halfway upgraded MGA8/cauldron system as Edward was experiencing

- second VB was updated to cauldron via the new wiki description
-> fully working and upgraded cauldron system 

Thus closing FIXED.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.