Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1064588 - downloading CSV list of packages for given cloned channel gives me list for original channel
Summary: downloading CSV list of packages for given cloned channel gives me list for o...
Keywords:
Status: NEW
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 22:40 UTC by Jan Hutař
Modified: 2014-02-12 22:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jan Hutař 2014-02-12 22:40:47 UTC
Description of problem:
Downloading CSV list of packages for given cloned channel gives me list of packages for original (i.e. cloned from) channel.


Version-Release number of selected component (if applicable):
spacewalk-java-2.1.148-1.el6.noarch


How reproducible:
always


Steps to Reproduce:
1. Create custom channel with, say, 940 packages + 40 more update packages
   with erratas - totaling to 980 packages
2. Clone that channel in original state without erratas
3. Go to Channels -> Manage Software Channels -> <your_cloned_channel> ->
   -> Packages -> List / Remove and note count of the packages below the table
   near the paginator - says "1 - 25 of 940"
4. Click to "Download CSV" there and notice you got CSV with 981 rows
   (one is for header)


Actual results:
In CSV file for cloned channel there is different number of packages (980) than what I can see in the webUI (940).


Expected results:
Numbers should match


Note You need to log in before you can comment on or make changes to this bug.