Bug 1101728

Summary:	Uploaded errata don't have the same attribute types as sync'd errata
Product:	[Retired] Pulp	Reporter:	Randy Barlow <rbarlow>
Component:	rpm-support	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	low	Docs Contact:
Priority:	medium
Version:	Master	CC:	skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-28 22:09:06 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 Randy Barlow 2014-05-27 19:40:46 UTC

I learned during the fixing of #1100848[0] that some of the attributes for an uploaded erratum don't have the same types as the synchronized versions. The only attribute I know this for sure about is "pushcount". For an uploaded erratum, pushcount will be an integer, but for a sync'd erratum it will be a string (of an integer).

We needed to fix [0] quickly so we went for making sure we only have strings to ElementTree. I believe the correct fix is to make sure we are consistent about the types that land in our database between synchronizing errata and uploading them. I personally believe that pushcount should be an int in the database, so for that case we should fix the synchronization code.

I set the severity to low because I cannot think of a use case that this would cause an issue for.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1100848

Comment 1 Brian Bouterse 2015-02-28 22:09:06 UTC

Moved to https://pulp.plan.io/issues/439