Created attachment 916630 [details] please note the 'here' hyperlink when the selected CV version binded to a content-host Description of problem: I was trying to remove a CV version from a selected env. While deletion, I found that some of content-hosts are also tied up with same version. So as per UI help tip, I clicked on 'Here' hyperlink and page starts refreshing and keep on refreshing. Following log entries generated during refresh in production.log --- Processing by Bastion::BastionController#index as HTML Parameters: {"search"=>"content_view:\"cv-rhel65-ks\" AND (environment:\"Library\" OR environment:\"Dev\")", "bastion_page"=>"content_views", "path"=>"2/versions/2/delete/undefined"} Rendered home/_submenu.html.erb (11.4ms) Rendered home/_user_dropdown.html.erb (3.4ms) Read fragment views/tabs_and_title_records-1 (0.3ms) Rendered home/_topbar.html.erb (19.8ms) Rendered layouts/base.html.erb (23.1ms) Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/engines/bastion/app/views/bastion/layouts/application.html.haml (28.2ms) Completed 200 OK in 57ms (Views: 29.9ms | ActiveRecord: 2.9ms) -- Version-Release number of selected component (if applicable): Satellite-6.0.3-RHEL-6-20140626.1, RC beta build How reproducible: always Steps to Reproduce: 1. create a CV, publish and promote it to next env ( e.g. dev) 2. register a content-host with same cv and env 'dev' or create a activation-key that uses same CV version 3. now try to delete the cv version Actual results: page starts refreshes as soon as we click on 'Here' hyperlink while removing CV version Please note that it appears at two places, 1) to disassociate content-host 2) to disassociate activation-key from the selected content-view. Please see attached screenshots for more context. Expected results: The 'here' hyper link should open the appropriate page Additional info:
Created attachment 916631 [details] same 'here' link appears on cv version removal and when selected CV version tied with a activationkey
Connecting redmine issue http://projects.theforeman.org/issues/6350 from this bug
(In reply to Walden Raines from comment #3) > Connecting redmine issue http://projects.theforeman.org/issues/6350 from > this bug Disregard, that was a mistake.
Created redmine issue http://projects.theforeman.org/issues/6821 from this bug
PR: https://github.com/Katello/katello/pull/4495
Moving to POST since upstream bug http://projects.theforeman.org/issues/6821 has been closed ------------- Walden Raines Applied in changeset commit:katello|e034e3957b24b855cf30aaf7a110091551cfa4de.
Failed. There are two scenarios mentioned in the bug: 1) to disassociate content-host - FAILED 2) to disassociate activation-key - PASSED Version Tested: GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23-1.el6_5.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23-1.el6_5.noarch * candlepin-tomcat6-0.9.23-1.el6_5.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.42-1.el6sat.noarch * foreman-compute-1.6.0.42-1.el6sat.noarch * foreman-gce-1.6.0.42-1.el6sat.noarch * foreman-libvirt-1.6.0.42-1.el6sat.noarch * foreman-ovirt-1.6.0.42-1.el6sat.noarch * foreman-postgresql-1.6.0.42-1.el6sat.noarch * foreman-proxy-1.6.0.30-1.el6sat.noarch * foreman-selinux-1.6.0.14-1.el6sat.noarch * foreman-vmware-1.6.0.42-1.el6sat.noarch * katello-1.5.0-30.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-installer-0.0.62-1.el6sat.noarch * openldap-2.4.23-34.el6_5.1.x86_64 * openldap-devel-2.4.23-34.el6_5.1.x86_64 * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch * pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch * pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch * pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch * pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch * pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch * pulp-server-2.4.1-0.5.rc1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
(In reply to sthirugn from comment #10) > Failed. > > There are two scenarios mentioned in the bug: > 1) to disassociate content-host - FAILED > 2) to disassociate activation-key - PASSED Sorry about that, missed that scenario. PR here: https://github.com/Katello/katello/pull/4638
The fix for this has already been merged to master.
Verified with: Satellite-6.1.0-RHEL-6-20150210.0 Sat6.1.0 beta snap2 Both links works perfectly, the one associated to content-host and the other associated to activation-key
This bug is slated to be released with Satellite 6.1.
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