Bug 21294 - Mageia 6: Repo metadata of packagekit inconsistent, fatal error
Summary: Mageia 6: Repo metadata of packagekit inconsistent, fatal error
Status: RESOLVED WORKSFORME
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-19 15:49 CEST by Ulrich Beckmann
Modified: 2017-07-19 21:33 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Screenshot of error message (34.32 KB, image/png)
2017-07-19 15:51 CEST, Ulrich Beckmann 		Details
CLI output of pkcon refresh (803 bytes, text/plain)
2017-07-19 15:53 CEST, Ulrich Beckmann 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ulrich Beckmann 2017-07-19 15:49:05 CEST 
Description of problem:
The system actualization with packagekit/plasma-pk-update fails with a fatal error. Metadata of Mageia-x86_64-tainted are missing.

Ulrich Beckmann
Comment 1 Ulrich Beckmann 2017-07-19 15:51:02 CEST 
Created attachment 9505 [details]
Screenshot of error message
Comment 2 Ulrich Beckmann 2017-07-19 15:53:27 CEST 
Created attachment 9506 [details]
CLI output of pkcon refresh
Comment 3 Ulrich Beckmann 2017-07-19 15:56:01 CEST 
cc'ing Neal Gompa

CC: (none) => ngompa13

Comment 4 Neal Gompa 2017-07-19 16:05:16 CEST 
I see the metadata in mirrors.kernel.org, so clearly it exists... http://mirrors.kernel.org/mageia/distrib/6/x86_64/media/tainted/release/repodata/

I'm not exactly sure what's happening here... Maybe a mirror has an incomplete replica of the metadata?
Comment 5 Ulrich Beckmann 2017-07-19 21:33:38 CEST 
After refreshing the cache
# pkcon refresh force -c -1
and reboot the error did not occur any longer.

Shortly after I tested in a virtual machine. First I had the same error, refreshing the cache and reboot cleaned the issue again.

Ulrich

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.