Description of problem: erratum list by order shows incorrect erratas 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 - Orgid=1 and Orgid=2. 2. Create a rhel65 repository in Orgid 1, sync it 3. Create another repository (with errata) in Orgid 2, sync it 3. Now run the cli command: hammer> erratum list --organization-id=2 --order 'updated ASC' (or) hammer> erratum list --organization-id=2 --order 'updated DESC' Actual results: The rhel65 erratas are showing up in Orgid 2 Expected results: Erratum list with org id should show errata for that org only Additional info: without '--order', it shows correct erratas hammer> erratum list --organization-id=2
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Works for me, please verify this is fixed on 6.2: First org: [vagrant@centos7-devel hammer-cli]$ hammer erratum list --organization "Default Organization" --order "title DESC" -------------------------------------|----------------|--------------|-------------------------------------------------- ID | ERRATA ID | TYPE | TITLE -------------------------------------|----------------|--------------|-------------------------------------------------- bc4db7ae-941a-420f-b192-f23a25acc52f | RHEA-2010:9999 | enhancements | test package enhancements 96b15571-8baf-49ac-b806-2dee089b4a78 | grinder_test_4 | enhancements | Test Errata referring to grinder_test_package-4.0 cd848511-691f-4fb0-b430-5a588375d3f2 | grinder_test_3 | enhancements | Test Errata referring to grinder_test_package-3.0 1181524c-99f0-433d-af20-35eabb96da46 | grinder_test_2 | enhancements | Test Errata referring to grinder_test_package-2.0 -------------------------------------|----------------|--------------|-------------------------------------------------- Second org: [vagrant@centos7-devel hammer-cli]$ hammer erratum list --organization "Org 2" --order "title DESC" ---|-----------|------|------ ID | ERRATA ID | TYPE | TITLE ---|-----------|------|------
I cannot reproduce this against satellite-6.2.0-18.0.el7sat.noarch. I get the same result as Stephen above.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501