Bug 1449374

Summary:	Package signing keys are not associated to package if same package is synced into multiple orgs
Product:	Red Hat Satellite 5	Reporter:	Jan Dobes <jdobes>
Component:	Satellite Synchronization	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	580	CC:	lhellebr, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-backend-2.5.3-124	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-21 12:10:50 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:
Bug Depends On:
Bug Blocks:	1358815

Description Jan Dobes 2017-05-09 20:08:39 UTC

Description of problem:
Package syncing code will not associate signing keys to package if the same package was previously synced into different/null organization.

Version-Release number of selected component (if applicable):
spacewalk-backend-2.5.3-123

How reproducible:
100%

Steps to Reproduce:
1. Sync one repo into channel in one org
2. Sync same repo into channel in second org

Actual results:
Signing key of some package on page /rhn/software/packages/Details.do?pid= will be "(Unknown)" in one org.
Content provider on page /rhn/channels/ChannelPackages.do?cid= will be unknown in one org.

Expected results:
Both orgs have packages with signing keys associated.

Additional info:
Most likely not a new behavior.

Comment 1 Jan Dobes 2017-05-09 22:26:04 UTC

fixed in spacewalk master:

17733eb5b5d5b66863cb0b3959a1475ef923d214

Comment 4 Lukáš Hellebrandt 2017-05-23 10:04:56 UTC

Verified with spacewalk-java-2.5.14-84.

Used reproducer from OP. Same packages now have signing key in every organization they are synced in.