[Spacewalk-list] Error syncing Fedora 26 channel

[Paschedag, Robert]

________________________________
Von: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> im Auftrag von Michael Watters <wattersm at watters.ws>
Gesendet: Donnerstag, 3. Mai 2018 20:39
An: spacewalk-list at redhat.com
Betreff: Re: [Spacewalk-list] Error syncing Fedora 26 channel


On 05/03/2018 10:10 AM, Paschedag, Robert wrote:



________________________________
Von: spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> <spacewalk-list-bounces at redhat.com><mailto:spacewalk-list-bounces at redhat.com> im Auftrag von Michael Watters <wattersm at watters.ws><mailto:wattersm at watters.ws>
Gesendet: Donnerstag, 3. Mai 2018 15:25
An: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Betreff: [Spacewalk-list] Error syncing Fedora 26 channel

When running spacewalk-repo-sync to sync a channel for Fedora 26 updates
I am getting an error as shown below.

09:16:46   Errata in repo: 3379.
09:16:55     Syncing 102 new errata to channel.
09:16:56 ERROR: Invalid severity: None
09:16:57 Sync of channel completed in 0:02:53.
09:16:57 Total time: 0:02:53

Does anybody know what would cause this?

You need to debug this. I'm pretty sure, that one errata is missing (or wrong formatted?) this "severity" within the XML file. In CentOS, this should be the updateinfo.xml.gz. But as it does not mention, "which" errata is causing the error, you could try to raise the debug level.

I would search for "Syncing * new errata" within the python modules and look for "log" messages....(to find the corresponding "debug level").

Robert

I'm not sure where those modules would be or how to change the debug level but I ran spacewalk-repo-sync using the --fail option and it looks like there is a Fedora advisory causing an error.

14:32:35 ERROR: Advisory FEDORA-2017-71a649ddf5 skipped because of empty package list (filtered).

Would this be caused by an issue upstream?

This "may" be caused by upstream Fedora....but it "might" be an error while parsing the XML for this errata. That's why I said...that you need to debug this. Or - in case it's an error upstream - just wait until this gets fixed.

Robert



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20180504/db672680/attachment.htm>