Bug 703381

Summary:	adding errata by errata.clone() api to cloned channel also adds non-relevant packages from that errata
Product:	Red Hat Satellite 5	Reporter:	Jan Pazdziora (Red Hat) <jpazdziora>
Component:	Docs Release Notes	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	high	Docs Contact:
Priority:	high
Version:	541	CC:	cperry, hdemonte, luc, mhideo, mosvald, pmutha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added. Revision 0-4	Story Points:	---
Clone Of:	678721	Environment:
Last Closed:	2011-06-16 22:34:19 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:	678721
Bug Blocks:	677505

Comment 1 Lana Brindley 2011-06-06 20:43:57 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Using the errata.clone() api to clone a specific errata to a cloned/custom channel would create a search through all packages belonging to an errata from all channels.

Consequence: The correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel.

Fix: The search no longer looks through unrelated channels

Result: Only the correct packages are added

Comment 2 Lana Brindley 2011-06-07 18:24:53 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -4,4 +4,7 @@
 
 Fix: The search no longer looks through unrelated channels
 
-Result: Only the correct packages are added+Result: Only the correct packages are added
+
+
+Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added.

Comment 3 Lana Brindley 2011-06-07 18:35:57 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,10 +1,3 @@
-Cause: Using the errata.clone() api to clone a specific errata to a cloned/custom channel would create a search through all packages belonging to an errata from all channels.
+Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added.
 
-Consequence: The correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel.
+Revision 0-4-
-Fix: The search no longer looks through unrelated channels
-
-Result: Only the correct packages are added
-
-
-Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added.