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.
DescriptionJustin Sherrill
2014-12-05 15:45:12 UTC
1. create a content view
2. add a repository with errata to it
3. Create a errata by id 'include' filter
4. go to 'Add' tab
5. Select some errata and click add errata
6. go to List/Remove page
Errors with traceback in ajax request:
ArgumentError: wrong number of arguments (2 for 1)
/home/vagrant/katello/app/controllers/katello/api/v2/errata_controller.rb:41:in `filter_by_content_view_filter'
/home/vagrant/katello/app/controllers/katello/concerns/api/v2/repository_db_content_controller.rb:54:in `index_relation'
/home/vagrant/katello/app/controllers/katello/concerns/api/v2/repository_db_content_controller.rb:26:in `index'
/home/vagrant/katello/app/controllers/katello/api/v2/errata_controller.rb:27:in `index'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.21/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.21/lib/abstract_controller/base.rb:167:in `process_action'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.21/lib/action_controller/metal/rendering.rb:10:in `process_action'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.21/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:560:in `block (3 levels) in _run__1919809952475137643__process_action__924257201874667573__callbacks'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_6497'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:326:in `around'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:310:in `_callback_around_3701'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_6497'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:482:in `block (2 levels) in _run__1919809952475137643__process_action__924257201874667573__callbacks'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_6496'
/home/vagrant/foreman/app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_6496'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:426:in `block in _run__1919
Moving to POST since upstream bug http://projects.theforeman.org/issues/8594 has been closed
-------------
Eric Helms
Applied in changeset commit:katello|d5b20135f861287bce2a38144fed5c364f457033.
Comment 6sthirugn@redhat.com
2015-05-01 17:01:14 UTC
Verified.
Version Tested: Satellite-6.1.0-RHEL-7-20150429.2
Verification steps:
1. create a content view
2. add a repository with errata to it
3. Create a errata by id 'include' filter
4. go to 'Add' tab
5. Select some errata and click add errata
6. go to List/Remove page - page displayed without errors (screenshot attached
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-2015:1592