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.
Descriptionsthirugn@redhat.com
2015-01-14 16:47:48 UTC
Description of problem:
hammer erratum list: Search with product options failed
Version-Release number of selected component (if applicable):
* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.37-1.el6.noarch
* candlepin-common-1.0.17-1.el6.noarch
* candlepin-selinux-0.9.37-1.el6.noarch
* candlepin-tomcat6-0.9.37-1.el6.noarch
* elasticsearch-0.90.10-7.el6.noarch
* foreman-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-compute-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-gce-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-libvirt-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-ovirt-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-postgresql-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-proxy-1.8.0-0.develop.201412301259gite2ce2a0.el6.noarch
* foreman-release-1.8.0-0.develop.201501051457git6529247.el6.noarch
* foreman-selinux-1.8.0-0.develop.201412151103gite2863e4.el6.noarch
* foreman-vmware-1.8.0-0.develop.201501051457git6529247.el6.noarch
* katello-2.1.0-1.201411061509gitb0b8f43.el6.noarch
* katello-certs-tools-2.0.1-1.el6.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-2.2.0-1.201412192027git113612b.el6.noarch
* katello-installer-base-2.2.0-1.201412192027git113612b.el6.noarch
* katello-repos-2.1.1-1.el6.noarch
* katello-server-ca-1.0-1.noarch
* openldap-2.4.23-32.el6_4.1.x86_64
* openldap-devel-2.4.23-32.el6_4.1.x86_64
* pulp-docker-plugins-0.2.1-0.2.beta.el6.noarch
* pulp-katello-0.3-3.el6.noarch
* pulp-nodes-common-2.5.1-1.el6.noarch
* pulp-nodes-parent-2.5.1-1.el6.noarch
* pulp-puppet-plugins-2.5.1-1.el6.noarch
* pulp-puppet-tools-2.5.1-1.el6.noarch
* pulp-rpm-plugins-2.5.1-1.el6.noarch
* pulp-selinux-2.5.1-1.el6.noarch
* pulp-server-2.5.1-1.el6.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.3.3-1.el6.noarch
* ruby193-rubygem-net-ldap-0.10.0-1.el6.noarch
* ruby193-rubygem-runcible-1.3.0-1.el6.noarch
How reproducible:
Always
Steps to Reproduce:
1. Create two orgs - Org1 and Org2.
2. Create a repository and product in both the orgs and sync them. Make sure both the repos have some erratas.
2. Now run the cli command to list the erratas from product-id = 1 in Org1
hammer> erratum list --product-id=1
Actual results:
All the erratas from both the Orgs are displayed
Expected results:
Erratas for the specific product displayed
Additional info:
Filtering with product name and organization id works fine:
# erratum list --product=testproduct1 --organization-id=3
So the existence of --product-id is there to aid in resolution of the repository name when the user specifies --repository=name.
The same issue occurs if you just specify --organization-id=X. This issue is likely seen throughout the katello hammer commands, and likely the non-hammer ones too.
I suggest we move this to 6.2 as more design and thought is needed.
What Justin wrote about cause of this issue is correct. Finding a good enough generic solution for all satellite commands will be quite difficult, but it's worth investigating.
The safe way is to fix this on per-command basis in option validation, where we can enforce certain combinations of parameters and inform users when they use incomplete combination.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.