Bug 150321

Summary:	Fix ConfigUploadAction, Add test
Product:	[Retired] Red Hat Network	Reporter:	Ken Ganong <kganong>
Component:	RHN/R&D	Assignee:	Ken Ganong <kganong>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	RHN Devel
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-08 13:52:34 UTC	Type:	---
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:	125080

Description Ken Ganong 2005-03-04 16:45:12 UTC

ConfigUploadAction has two ActionChildren, ConfigDateDetails and
ConfigDateFileAction.  Both use actionId as a primary key.  This
should work for ConfigDateDetails (test will indicate that problem),
but it will not work for ConfigDateFileAction because
ConfigUploadAction contains a set of them, meaning multiple
ConfigDateFileActions with the same primary key.

There needs to be a test for creating, committing, and looking up a
ConfigUploadAction.

Comment 1 Ken Ganong 2005-03-04 20:15:22 UTC

Correct, three ActionChildren,  ConfigChannelAssociation.  This third
one also has no mapping file.

Comment 2 Ken Ganong 2005-03-08 13:52:34 UTC

Tested whether ConfigUploadActions could be created, committed, and
looked up.  Added a composite key to ConfigDateFileAction.  Found that
the equals method of ConfigChannelAssociation wouldn't allow the
lookup of more than one ConfigChannelAssociation and fixed that. 
ConfigChannelAssociations mapping is achieved through a composite key
in Action.hbm.xml.