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.
In the "Changeset History" tab, selecting changesets with blacklisted packages from a previously promoted changeset raises an error:
"undefined method 'find repos' for #."
This fix corrects rendering logic. Changesets with previously blacklisted packages now display without causing an error.
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:
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.
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