Red Hat Bugzilla – Bug 1271006
Unable to import errata for Fedora 22 Updates
Last modified: 2017-09-28 14:10:19 EDT
Description of problem:
On repo-sync of Fedora 22 updates channel, errata is detected but not imported. sync log in Additional info.
Version-Release number of selected component (if applicable):
Spacewalk 2.4 on Fedora 22, x86_64
Can reproduce on both fresh installs and multiple synchronizations
Steps to Reproduce:
1. Add fedora 22 channels via spacewalk-utils/common-channels
2. Synchronize Fedora 22 Updates repo
Log indicates errata is detected but is not imported
Errata is detected and imported
Sync log as follows:
Sync started: Mon Oct 12 17:11:41 2015
['/usr/bin/spacewalk-repo-sync', '--channel', 'fedora22-x86_64-updates', '--type', 'yum']
Repo URL: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64
Packages in repo: 15691
No new packages to sync.
Repo https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64 has comps file comps.xml.
Repo https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64 has 2372 errata.
ERROR: 'NoneType' object has no attribute 'isdigit'
Total time: 0:07:27
I have successfully reproduced your problem and you are right, it does not import due to missing "issue date" in one item. I'm afraid that we are not able to help you with this issue, because it's Fedora 22 Updates repo 'bug'. You will make it working once the missing item is full-filled.
I'd suggest you writing a ticket/bug report on 'Fedora 22 Updates'. At the time they provide the update it should be possible to do import without any problems.
I've created a ticket on Fedora infrastructure. Check status on "https://fedorahosted.org/fedora-infrastructure/ticket/4983"
*** Bug 1276523 has been marked as a duplicate of this bug. ***
According to https://github.com/fedora-infra/bodhi/issues/718 the issue have been fixed in fc22 repository metadata. Would you, please, confirm, you can successfully sync fc22 repository?
Apologies for the long delay in reply; I can confirm the issue is resolved.
(In reply to max from comment #5)
> I can confirm the issue is resolved.
Thank you. I'm closing the bug as CURRENTRELEASE.
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.