Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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 ***