Created attachment 1344337 [details] Screenshot Description of problem: When using bulk errata apply from errata page, it fails saying "No content has been provided", though content hosts were properly selected. From production.log 2017-10-27 10:29:47 e01b768d [app] [I] Started PUT "/api/v2/hosts/bulk/install_content" for 10.36.117.171 at 2017-10-27 10:29:47 -0400 2017-10-27 10:29:47 e01b768d [app] [I] Processing by Katello::Api::V2::HostsBulkActionsController#install_content as JSON 2017-10-27 10:29:47 e01b768d [app] [E] Katello::HttpErrors::BadRequest: No content has been provided. | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.4.5.16/app/controllers/katello/api/v2/hosts_bulk_actions_controller.rb:299:in `validate_content_action' Version-Release number of selected component (if applicable): Satellite 6.3 Snap 21: * katello-3.4.5-5.el7sat.noarch * foreman-1.15.6.1-1.el7sat.noarch * satellite-6.3.0-21.0.beta.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Add content hosts with outdated package and repository with available errata 2. Go to Content -> Errata. Select an erratum -> Content Hosts tab. 3. Select Content Hosts and apply the erratum. Actual results: Error "No content host has been provided" Expected results: Errata should be applied to selected content hosts. Additional info:
Apparently it was fixed in snap 22: * foreman-1.15.6.3-1.el7sat.noarch * katello-3.4.5-6.el7sat.noarch * satellite-6.3.0-21.0.beta.el7sat.noarch
Created redmine issue http://projects.theforeman.org/issues/21521 from this bug
This may have been fixed by BZ 1506846. I'm moving to ON_QA for verification.
VERIFIED. @satellite-6.3.0-21.0.beta.el7sat.noarch foreman-1.15.6.9-1.el7sat.noarch katello-3.4.5-6.el7sat.noarch by manual reproducer described in comment#0 2. Selected RHBA-2017:2926 openssh bug fix update (RHEL7.4) 3. Chose to apply it to 4 hosts (RHEL7.3) 4 task(s), 4 success, 0 fail @HOSTs: # rpm -q openssh openssh-7.4p1-13.el7_4.x86_64 >>> errata applied successfully on the selected hosts
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/RHSA-2018:0336