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.