Bug 717375 - Repos for all environments shown when it should only show for given env
Summary: Repos for all environments shown when it should only show for given env
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-06-28 17:39 UTC by Jeff Weiss
Modified: 2019-09-26 13:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 17:47:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeff Weiss 2011-06-28 17:39:01 UTC 
Description of problem:
In the promotions UI, if you drill down to repos, you'll see a repo for both the current env and the promoted one.  Justin Sherrill looked into it and saw the call in the code is

 Product.first.repos(@environment)

but it seems to return the repos for all the environments.


Version-Release number of selected component (if applicable):
katello-0.1.49-1.git.44.5815b3f.fc14.noarch

How reproducible:


Steps to Reproduce:
1. Create product/repo/env
2. Promote the product to new env
3. On promotions page, drill down in Locker env down to the product you promoted, click on Repositories. 
  
Actual results:
2 identically named repos shown, one with add button, one with "Promoted" next to it.

Expected results:
1 repo shown.

Additional info:
Comment 1 Tomas Strachota 2011-09-14 09:21:18 UTC 
Fixed long time ago in

commit 1b346ddd4c5491d338ca7c5dd085986296ee4172
Author: Tomas Strachota <tstrachota>
Date:   Wed Jul 20 17:32:38 2011 +0200
Comment 2 Corey Welton 2011-09-22 14:27:58 UTC 
QA Verified, only the repo with "Promoted" next to it appears.
Comment 5 Mike McCune 2013-08-16 17:56:36 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.