Bug 526733

Summary: Errata Cloning Problem via WebUI
Product: [Community] Spacewalk Reporter: Andy Speagle <andy.speagle>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.6CC: tlestach
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: 2011-02-08 08:41:09 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: 653453    

Description Andy Speagle 2009-10-01 15:06:50 UTC 
Description of problem:

When publishing cloned errata via the WebUI, if the channel to which I publish the cloned errata does not already have the packages associated with the cloned errata, then the packages are stripped from the cloned errata and the packages are not pushed to the target channel.

However, if the channel already has the packages associated with the cloned errata to be published, it succeeds as normal.  Also, when I do errata cloning via the API [server.errata.clone ()], it works perfectly.  It clones and publishes the errata with all packages as expected.

Version-Release number of selected component (if applicable):
Spacewalk v0.6

How reproducible:
I can demonstrate this every time.

Steps to Reproduce:  (via the WebUI)
1. Find an erratum for which the associated packages are not already pushed to a destination channel for the erratum.
2. Clone the erratum.
3. Publish the erratum to the target channel.
  
Actual results:
Note that the packages previously associated with the erratum are no longer listed in the cloned erratum and were NOT pushed to the target channel.

Expected results:
Published cloned errata should still have their associated packages listed and said packages are pushed to channels to which the cloned errata were published.

Additional info:
This functionality works perfectly via the API.
Comment 1 Jan Pazdziora 2010-11-19 16:04:58 UTC 
Mass-moving to space13.
Comment 2 Tomas Lestach 2011-01-28 13:54:01 UTC 
This has been resolved long time ago.
This works on current nightly. Setting to MODIFIED.
Comment 3 Tomas Lestach 2011-02-03 12:21:22 UTC 
Moving ON_QA ...
Comment 4 Tomas Lestach 2011-02-08 08:41:09 UTC 
This bug has been fixed in Spacewalk 1.3.