Bug 1478754

Summary:	yum-deprecated has issues with the new xmlns format and aborts operation instantly
Product:	[Fedora] Fedora	Reporter:	Ali Akcaagac <aliakc>
Component:	mirrormanager	Assignee:	Pierre-YvesChibon <pingou>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	adrian, jonstanley, pingou, puiterwijk
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-07 06:33:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ali Akcaagac 2017-08-06 23:03:51 UTC

Recently one of our infrastructure systems (not related to Fedora) broke down because yum-deprecated, which we still depend and rely on for "reasons" had issues downloading the metadata.xml and repodata.xml files from RPMFusion.

I instantly went there and opened a bugreport about his issue because yum aborted with a "no timestamp" error message.

After some conversation with the admins and other participants, it was said that there was some changes in the infrastructure and mirrormanager etc...

Unfortunately this situation leaves us in a broken state because tools we rely and depend on are not working anymore.

Also the question about how LTS RHEL deals with that issue was thrown in the room.

https://bugzilla.rpmfusion.org/show_bug.cgi?id=4616

Something needs to be fixed here... urgently...

Comment 1 Adrian Reber 2017-08-07 06:33:34 UTC

This has been fixed in MirrorManager by reverting the change:

https://github.com/fedora-infra/mirrormanager2/pull/214