Description of problem: Installable errata is not listed in Content -> Errata page Version-Release number of selected component (if applicable): Satellite 6.1 GA Snap 6 How reproducible: Always Steps to Reproduce: 1. Sync few products, register few content hosts 2. Navigate to Content -> errata page and try to filter the following: - Installable errata for a repo - Applicable and Installable errata for a repo Actual results: No results are returned for both the mentioned scenarios Expected results: I have installable errata for the selected repo which should be displayed. Additional info: This failed in CLI too: failed: hammer> erratum list --organization-id=3 --repository-id=6 --errata-restrict-applicable=false --errata-restrict-installable=true ---|-----------|------|------ ID | ERRATA ID | TYPE | TITLE ---|-----------|------|------ failed: hammer> erratum list --organization-id=3 --repository-id=6 --errata-restrict-applicable=true --errata-restrict-installable=true ---|-----------|------|------ ID | ERRATA ID | TYPE | TITLE ---|-----------|------|------ passed: hammer> erratum list --organization-id=3 --repository-id=6 --errata-restrict-applicable=true --errata-restrict-installable=false ** This displayed errata info as expected ** passed: (without repository id) hammer> erratum list --organization-id=3 --errata-restrict-applicable=true --errata-restrict-installable=true ** This displayed errata info as expected **
Created redmine issue http://projects.theforeman.org/issues/10681 from this bug
PR: https://github.com/Katello/katello/pull/5267
Moving to POST since upstream bug http://projects.theforeman.org/issues/10681 has been closed ------------- Walden Raines Applied in changeset commit:katello|fcd7bcc806015514fc76215597d393d985919da3.
Verified in Sat 6.1 GA Snap 8. Now I see Installable errata listed in Content -> Errata page. And also the failed CLI scenarios mentioned in the bugs works fine now. hammer> erratum list --organization-id=3 --repository-id=1 --errata-restrict-applicable=false --errata-restrict-installable=true -------------------------------------|----------------|-------------|---------------------------------------------------------------- ID | ERRATA ID | TYPE | TITLE -------------------------------------|----------------|-------------|---------------------------------------------------------------- 1aaef134-fdb2-4686-b220-27f86840c287 | RHSA-2015:1090 | security | Important: wpa_supplicant security and enhancement update aae3209a-62eb-4a30-8c8c-e177bbefeef4 | RHSA-2015:1072 | security | Moderate: openssl security update d6780ffc-49a0-4e64-b494-c79b977ea81c | RHBA-2015:0964 | bugfix | ca-certificates bug fix and enhancement update ... ... hammer> erratum list --organization-id=3 --repository-id=1 --errata-restrict-applicable=true --errata-restrict-installable=true -------------------------------------|----------------|-------------|---------------------------------------------------------------- ID | ERRATA ID | TYPE | TITLE -------------------------------------|----------------|-------------|---------------------------------------------------------------- 1aaef134-fdb2-4686-b220-27f86840c287 | RHSA-2015:1090 | security | Important: wpa_supplicant security and enhancement update aae3209a-62eb-4a30-8c8c-e177bbefeef4 | RHSA-2015:1072 | security | Moderate: openssl security update ... ... But it is worth to note that there is one outstanding bug in this scenario which is noted in https://bugzilla.redhat.com/show_bug.cgi?id=1232331
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.