Bug 1269434 - unable to filter puppet-module as per repo or org id
Summary: unable to filter puppet-module as per repo or org id
Keywords:
Status: CLOSED DUPLICATE of bug 1283173
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-07 10:48 UTC by Kedar Bidarkar
Modified: 2017-02-23 19:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-22 17:20:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12092 0 None None None 2016-04-22 15:35:34 UTC

Description Kedar Bidarkar 2015-10-07 10:48:37 UTC
Description of problem:

unable to filter puppet-module as per repo or org id, it always returns all the puppet-modules ever installed on the satellite6.


Version-Release number of selected component (if applicable):
sat6.1.1 and also sat6.1.3

How reproducible:
always

Steps to Reproduce:
1. create a puppet-module repo in Org A
2. create another puppet-module repo in Org B
3. hammer -u admin -p changeme puppet-module list --organization-id <org-id>
4. hammer -u admin -p changeme puppet-module list --repository-id <repo-id>

Actual results:
Does not list as per the org or repo , but lists all the puppet-modules in a satellite6.

Expected results:
should list only as per the org or repo , but not list all the puppet-modules

Additional info:

Comment 2 Bryan Kearney 2015-10-07 21:00:17 UTC
Created redmine issue http://projects.theforeman.org/issues/12092 from this bug

Comment 3 Bryan Kearney 2015-10-14 13:21:19 UTC
Upstream bug component is API

Comment 4 Brad Buckingham 2015-12-22 17:20:29 UTC
This bug appears to have been solved by bug 1283173; therefore, I am going to close this one as a duplicate.  I have tested it on the upstream and the behavior is now as expected:

(Note: 2 orgs, each org has 1 puppet module)

hammer> puppet-module list --organization-id 1
---|------|------------|--------
ID | NAME | AUTHOR     | VERSION
---|------|------------|--------
1  | git  | theforeman | 1.3.0  
---|------|------------|--------

hammer> puppet-module list --organization-id 3
---|-------|---------|--------
ID | NAME  | AUTHOR  | VERSION
---|-------|---------|--------
2  | ovirt | jcannon | 0.0.4  
---|-------|---------|--------

hammer> puppet-module list --repository-id 7
---|------|------------|--------
ID | NAME | AUTHOR     | VERSION
---|------|------------|--------
1  | git  | theforeman | 1.3.0  
---|------|------------|--------

hammer> puppet-module list --repository-id 8
---|-------|---------|--------
ID | NAME  | AUTHOR  | VERSION
---|-------|---------|--------
2  | ovirt | jcannon | 0.0.4  
---|-------|---------|--------

*** This bug has been marked as a duplicate of bug 1283173 ***


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