Bug 28573

Summary:	mgaapplet update to kernel-5.10.20-2 not resilient
Product:	Mageia	Reporter:	peter lawford <petlaw726>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	fri, ouaurelien
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	1st urpmi --auto-update 2nd urpmi --auto-update return of dnf --refresh upgrade 3rd urpmi --auto-update 4th urpmi --auto-update

Description peter lawford 2021-03-10 13:44:23 CET

Description of problem:I have received an invitation to update one of my systems (I have 3 mageia7 on my machine) to kernel-5.10.20-2; as I was busy at this moment, I have quitted; usually, the applet commes back immediately, but this time this applet never came back; why? furthermore:
[root@mga6-64 alain4]# LANG=C urpmi --auto-update
medium "Core Release" is up-to-date
medium "Core Updates" is up-to-date
medium "Nonfree Release" is up-to-date
medium "Nonfree Updates" is up-to-date
medium "Tainted Release" is up-to-date
medium "Tainted Updates" is up-to-date
medium "Core 32bit Release" is up-to-date
medium "Core 32bit Updates" is up-to-date
medium "Nonfree 32bit Release" is up-to-date
medium "Nonfree 32bit Updates" is up-to-date
medium "Tainted 32bit Release" is up-to-date
medium "Tainted 32bit Updates" is up-to-date
Packages are up to date
[root@mga6-64 alain4]# 
showing that this kernel update was a "ghost" update
the problem is that I already ran this update with "urpmi --auto-update" on one of my system mageia7 on which the repos "core-update-testing" is disabled: how was it possible? is updating to kernel-5.10.20-2 dangerous? 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 peter lawford 2021-03-10 14:17:45 CET

I have run five times, 3 minutes apart, the commands urpmi --auto-update and dnf --refresh upgrade: see the returns as attached files

Comment 2 peter lawford 2021-03-10 14:26:07 CET

Created attachment 12443 [details]
1st urpmi --auto-update

Comment 3 peter lawford 2021-03-10 14:26:52 CET

Created attachment 12444 [details]
2nd urpmi --auto-update

Comment 4 peter lawford 2021-03-10 14:27:35 CET

Created attachment 12445 [details]
return of dnf --refresh upgrade

Comment 5 peter lawford 2021-03-10 14:28:19 CET

Created attachment 12446 [details]
3rd urpmi --auto-update

Comment 6 peter lawford 2021-03-10 14:28:51 CET

Created attachment 12447 [details]
4th urpmi --auto-update

Comment 7 peter lawford 2021-03-10 14:29:34 CET

as you can see the returne of these commands contradicts one each others

Comment 8 Morgan Leijström 2021-03-10 15:49:40 CET

I think you need to use an up to date mirror.

Unfortunately coffee have stopped updating, and so half of our mirrors syncing from it :(

CC: (none) => fri

Comment 9 peter lawford 2021-03-10 17:40:34 CET

(In reply to Morgan Leijström from comment #8)
> I think you need to use an up to date mirror.
> 
> Unfortunately coffee have stopped updating, and so half of our mirrors
> syncing from it :(

yes, but how to find up-to-date mirrors?

Comment 10 Morgan Leijström 2021-03-10 17:47:34 CET

http://mirrors.mageia.org/status

On dev list an hour ago tmb reported coffe is rolling again, so in a few hours all should have catched up.

Comment 11 peter lawford 2021-03-10 18:02:04 CET

(In reply to Morgan Leijström from comment #10)
> http://mirrors.mageia.org/status
> 
> On dev list an hour ago tmb reported coffe is rolling again, so in a few
> hours all should have catched up.

great!

Comment 12 Aurelien Oudelet 2021-03-13 16:53:05 CET

Peter, in this case, you rely on $MIRRORLIST functionality from URPMI.

If the mirror chosen by script to update is not fully synchronized or stale, this can happen like your Attachment 12446 [details].

To prevent such error, you should remove all repositories from URPMI by using drakrpm-edit-media. Then, choose to Add a specific media mirror from File menu.
Then select in France free.fr mirror which gives best results, you can also choose distrib-coffee.

How about now?

CC: (none) => ouaurelien
Status: NEW => NEEDINFO

Comment 13 Aurelien Oudelet 2021-04-06 20:12:42 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEEDINFO => RESOLVED
Resolution: (none) => OLD