Bug 588901 - listLatestUpgradablePackages returns too many packages
listLatestUpgradablePackages returns too many packages
Product: Spacewalk
Classification: Community
Component: API (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Joshua Roys
Red Hat Satellite QA List
Depends On:
Blocks: space12
  Show dependency treegraph
Reported: 2010-05-04 15:24 EDT by Joshua Roys
Modified: 2010-11-19 11:16 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-19 11:16:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to fix (4.10 KB, patch)
2010-05-04 15:27 EDT, Joshua Roys
no flags Details | Diff

  None (edit)
Description Joshua Roys 2010-05-04 15:24:39 EDT
Description of problem:
package arch is not taken into account in the SQL query underlying this API call

Version-Release number of selected component (if applicable):
git HEAD

How reproducible:
python swapi.py -A $SYSTEMID -s $SERVER -u $USER system.listLatestUpgradablePackages

Steps to Reproduce:
1. push glibc.i386, .i686, .x86_64 to a channel.
2. have .i686 and .x86_64 installed on a host subscribed to above channel
3. execute API call
Actual results:
all 3 glibc packages are returned as candidates for updating

Expected results:
only .i686 and .x86_64 get returned as updates

Additional info:
Comment 1 Joshua Roys 2010-05-04 15:27:13 EDT
Created attachment 411383 [details]
patch to fix
Comment 2 Joshua Roys 2010-05-04 15:41:22 EDT
Fixed in spacewalk.git master 3f6829d6aa6f06cee89e235f2519fb128a7ab8e7
Comment 3 Joshua Roys 2010-05-05 11:52:51 EDT
Follow-up fix in 7bd8078b7dc3483f97245f8049ef8f7f688bce83
This will return the correct to_package_id
Comment 4 Jan Pazdziora 2010-10-27 04:32:23 EDT
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.
Comment 6 Jan Pazdziora 2010-11-19 11:16:34 EST
With Spacewalk 1.2 released, marking as CLOSED CURRENTRELEASE.


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