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.

Bug 827546

Summary: Selecting changeset from 'changeset history' tab raising "undefined method `find_repos' for #"
Product: Red Hat Satellite Reporter: Chris Pelland <cpelland>
Component: WebUIAssignee: Jason E. Rist <jrist>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: cpelland, jlaska, mmccune, omaciel, pchalupa, sachua, sghai
Target Milestone: UnspecifiedKeywords: Triaged, ZStream
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When users select a changeset from 'changeset history' tab, it raises an "undefined method 'find_repos' for #" error message. This update allows users to select and promote changeset from 'changeset history' tab without the error message.
Story Points: ---
Clone Of: 807288 Environment:
Last Closed: 2012-07-10 07:24:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 807288    
Bug Blocks:    
Attachments:
Description Flags
Promoting blacklisted packages
none
no error raised while clicking the changeset that we created for promotion of blacklisted packages none

Comment 4 Sachin Ghai 2012-06-07 05:45:47 UTC
Verified with latest puddle:

[root@dhcp201-221 ~]# rpm -qa | grep katello-0
katello-0.1.313-1.el6_3.noarch


I tried to promote the balcklisted packages and checked the changeset under changeset history tab. No error raised on UI.

for ex: Here I created a re-promote changeset and promoted 2 blacklisted packages as per attachment. After promotion, I checked the 're-promote' chnageset under 'changeset history' tab and no 'undefined method' error raised.

Comment 5 Sachin Ghai 2012-06-07 05:46:59 UTC
Created attachment 590078 [details]
Promoting blacklisted packages

Comment 6 Sachin Ghai 2012-06-07 05:48:11 UTC
Created attachment 590079 [details]
no error raised while clicking the changeset that we created for promotion of blacklisted packages

Comment 7 sachua 2012-06-13 02:09:17 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When users select a changeset from 'changeset history' tab, it raises an "undefined method 'find_repos' for #" error message. This update allows users to select and promote changeset from 'changeset history' tab without the error message.

Comment 9 errata-xmlrpc 2012-07-10 07:24:49 UTC
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/RHBA-2012-1062.html

Comment 10 Mike McCune 2013-08-16 17:56:01 UTC
getting rid of 6.0.0 version since that doesn't exist