Red Hat Bugzilla – Bug 1191662
Repository delete results in failed task
Last modified: 2016-04-22 11:51:04 EDT
Deleting a Repository results in a failed task: <pre> NoMethodError undefined method `can?' for nil:NilClass --- - /home/vagrant/katello/app/models/katello/authorization.rb:22:in `authorized?' - /home/vagrant/katello/app/models/katello/authorization/product.rb:30:in `editable?' - /home/vagrant/katello/app/models/katello/authorization/repository.rb:25:in `deletable?' - /home/vagrant/katello/app/models/katello/repository.rb:474:in `assert_deletable' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:407:in `_run__3721688161599193244__destroy__1563448023527611882__callbacks' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:405:in `__run_callback' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:385:in `_run_destroy_callbacks' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.21/lib/active_support/callbacks.rb:81:in `run_callbacks' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.21/lib/active_record/callbacks.rb:254:in `destroy' - /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.21/lib/active_record/transactio </pre>
Created from redmine issue http://projects.theforeman.org/issues/8598
Moving to POST since upstream bug http://projects.theforeman.org/issues/8598 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|0b489b5175df140f45eb9812d92d5a53b6e811ca.
Verified against two Satellite 6.0.8 applications, one running on RHEL 6.6 and the other on RHEL 7.0. They have package ruby193-rubygem-katello-1.5.0-95.el{6,7}sat.noarch installed, respectively. I am able to create a repository and delete it successfully. Fetching a deleted repository returns a response containing this message: u'{"displayMessage":"404 Resource Not Found","errors":["404 Resource Not Found"]}'
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-2015:0247