Hide Forgot
Description of problem: I applied package filters on a custom product and later tried to promote the product. Product was promoted successfully with applied filters. Later I tried to re-promote the blacklisted packages to same env. Promotion was successful but none of the blacklisted packages were promoted to next env. And I think it is expected. However when I selected the changeset created for blacklist package promotion from the changeset history tab, UI raised following error: undefined method `find_repos' for # Version-Release number of selected component (if applicable): pulp-1.0.0-6.el6.noarch katello-0.1.306-1.el6.noarch katello-glue-candlepin-0.1.306-1.el6.noarch candlepin-0.5.26-1.el6.noarch katello-cli-0.1.107-1.el6.noarch How reproducible: always Steps to Reproduce: 1. Create a product/repo and sync it ( Let's say pulp repo) 2. created package filter and filter out gofer and grinder packages and select the pulp product. 3. Create a changeset1 and promote the pulp product. 4. All packages should be promoted except gofer and grinder 5. Now create another changeset2 and add blacklisted packages ( gofer, grinder) to new changeset2 and promote them. Note: Promotion should be successful but in actual none of the blacklisted package should be promoted 6. Go to changeset history tab and select changeset2 Actual results: undefined method `find_repos' for # Expected results: There shouldn't be any error on UI after selecting the changeset from changeset history tab Additional info:
Created attachment 573054 [details] selecting changeset from changeset history tab raised undefined error
Yes, its still reproducible in latest katello build: katello-0.1.310-1.el6_2.noarch This defect is not a blocker as its not blocking any function/feature, however if its a easy fix then I think its good to include in V1.0. This issue appears with 'Changeset history' tab. And its a separate tab in UI. So customer will surely check/try this tab once. Again good to include if its a easy fix.
Moving to 1.0.1 since it blocks the usage of the Changeset History page
*** Bug 820882 has been marked as a duplicate of this bug. ***
fixed in 90800a766f6b69e8ec506c975a6ca6bcb12ad9d6
Verified using: * candlepin-0.7.8-1.el6cf.noarch * candlepin-selinux-0.7.8-1.el6cf.noarch * candlepin-tomcat6-0.7.8-1.el6cf.noarch * katello-1.1.12-7.el6cf.noarch * katello-all-1.1.12-7.el6cf.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.1.8-1.el6cf.noarch * katello-cli-1.1.8-4.el6cf.noarch * katello-cli-common-1.1.8-4.el6cf.noarch * katello-common-1.1.12-7.el6cf.noarch * katello-configure-1.1.9-3.el6cf.noarch * katello-glue-candlepin-1.1.12-7.el6cf.noarch * katello-glue-pulp-1.1.12-7.el6cf.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.1.1-1.el6cf.noarch * pulp-1.1.12-1.el6cf.noarch * pulp-common-1.1.12-1.el6cf.noarch * pulp-selinux-server-1.1.12-1.el6cf.noarch
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. http://rhn.redhat.com/errata/RHSA-2012-1543.html