Bug 25139

Summary: Inconsistent mirror status using dnf with updates_testing enabled
Product: Infrastructure Reporter: Ulrich Beckmann <bequimao.de>
Component: OthersAssignee: Sysadmin Team <sysadmin-bugs>
Status: REOPENED --- QA Contact:
Severity: normal    
Priority: Normal CC: ghibomgx, pterjan, sysadmin-bugs, tmb
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Linux   
See Also: https://bugs.mageia.org/show_bug.cgi?id=24726
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: CLI output of test upgrade
CLI output of test upgrade
CLI output of test upgrade
CLI output of test upgrade
CLI output of test upgrade
CLI output of test upgrade
Occurrence: Testing 29357 glibc

Description Ulrich Beckmann 2019-07-17 08:09:23 CEST
I cannot upgrade using dnf with updates_testing enabled.

There are multiple mismatches between metadata and packages listed in the QA database since a few days. Kernel 5.1.17 is offered. Version no. should be 5.1.18.

Best regards,
Ulrich
Comment 1 Ulrich Beckmann 2019-07-17 08:10:39 CEST
Created attachment 11193 [details]
CLI output of test upgrade
Ulrich Beckmann 2019-07-17 08:17:33 CEST

Version: 7 => unspecified
Component: RPM Packages => Others
Assignee: bugsquad => sysadmin-bugs
Product: Mageia => Infrastructure
CC: (none) => sysadmin-bugs

Ulrich Beckmann 2019-07-17 08:21:15 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=24726
CC: (none) => tmb

Comment 2 Ulrich Beckmann 2019-07-21 10:30:09 CEST
Works again since Friday morning, 19-07-2019.

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

Comment 3 Ulrich Beckmann 2019-08-01 21:00:55 CEST
Created attachment 11234 [details]
CLI output of test upgrade

Again another mismatch since about 2 days.

# urpmi --auto-upgrade works as tested in a VM.
# dnf upgrade works with upgrades_testing disabled.

As I said before, dnf metadata should be generated and monitored automatically.

Ulrich

Attachment 11193 is obsolete: 0 => 1

Comment 4 Ulrich Beckmann 2019-08-01 21:02:06 CEST
Reopened

Resolution: WORKSFORME => (none)
Status: RESOLVED => REOPENED

Comment 5 Ulrich Beckmann 2019-08-05 11:24:40 CEST
Working again since Sunday evening, 2019-08-04.
Comment 6 Ulrich Beckmann 2019-08-28 13:34:31 CEST
Created attachment 11265 [details]
CLI output of test upgrade

Another mismatch when trying to test https://bugs.mageia.org/show_bug.cgi?id=25349

mesa-19.1.5-2.mga7 should be available since 2019-08-25.

Ulrich
Comment 7 Ulrich Beckmann 2019-08-31 16:55:42 CEST
Working again since 2019-08-29. Upgraded 3 times (1 real hardware, 2 VMs)
Comment 8 Ulrich Beckmann 2019-09-11 08:34:08 CEST
Created attachment 11272 [details]
CLI output of test upgrade

Another mismatch spotted on 2019-09-09.

kernel-desktop-5.2.13-1.mga7-1-1.mga7.x86_64.rpm should be available in update-testing since 2019-09-08.
Comment 9 Ulrich Beckmann 2019-09-15 08:34:41 CEST
Working again since 2019-09-13. 

I guess that metadata are refreshed and synced, when a bunch of packages is moved from updates_testing to testing.
Comment 10 Ulrich Beckmann 2019-11-13 20:13:56 CET
Created attachment 11355 [details]
CLI output of test upgrade

Another mismatch on 11/11, which is not yet resolved 2 days later.

BTW there were other issues not documented here.
Comment 11 Ulrich Beckmann 2020-08-12 16:08:59 CEST
Created attachment 11802 [details]
CLI output of test upgrade

Kernel 5.7.14-1.mga7 should be available since 2020-08-07, but still it is not.

This is a long standing issue. I did not comment it at any occurrence.

Ulrich
Comment 12 Giuseppe Ghibò 2020-08-12 16:38:26 CEST
Are you using mirrorlist or baseurl in /etc/yum.repos.d/mageia-x86_64.repo? What if you use dnf update --refresh?

CC: (none) => ghibomgx

Comment 13 Ulrich Beckmann 2020-08-12 19:15:14 CEST
I use mirrorlist as it is default. Never changed anything in this regard.

You see the output of # dnf upgrade --refresh (nothing to do)
-> attachment comment#11.
Giuseppe Ghibò 2020-08-12 20:05:48 CEST

CC: (none) => pterjan

Comment 15 Ulrich Beckmann 2020-08-17 15:54:48 CEST
Yesterday # dnf upgrade --refresh ran a successful upgrade of 60 packages.

It looks as if metadata are refreshed manually when shifting packages from updates_testing to testing.
Comment 16 Ulrich Beckmann 2021-08-13 16:22:24 CEST
Created attachment 12900 [details]
Occurrence: Testing 29357 glibc

Still valid in current MGA 8 updates_testing

The bugreport is already set ok. I still cannot download the package list.

Attachment 11234 is obsolete: 0 => 1
Attachment 11265 is obsolete: 0 => 1
Attachment 11272 is obsolete: 0 => 1

Comment 17 Ulrich Beckmann 2021-08-13 16:30:49 CEST
(In reply to Ulrich Beckmann from comment #15)
> Yesterday # dnf upgrade --refresh ran a successful upgrade of 60 packages.
> 
> It looks as if metadata are refreshed manually when shifting packages from
> updates_testing to testing.

* shifting packages from updates_testing to updates.