Bug 1313771 - Editing composite content view shows incorrect repositories
Summary: Editing composite content view shows incorrect repositories
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-02 10:25 UTC by Brad Buckingham
Modified: 2019-09-26 18:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 18:01:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Brad Buckingham 2016-03-02 10:25:33 UTC
"ghost" repository in content view
   1. created 3 CVs (note composite1 and 2 both have same repo) and publish
    Name,Label,Organization,Composite,Repositories or Composites,Lifecycle Environments
    component1,component1,Mega Corporation,No,Red Hat Satellite Tools 6.1 for RHEL 7 Server RPMs x86_64,"Library,Baseline"
    component2,component2,Mega Corporation,No,Red Hat Satellite Tools 6.1 for RHEL 7 Server RPMs x86_64,"Library,Baseline"
    composite,composite,Mega Corporation,Yes,"component1,component2","Library,Baseline"
   2. composite fails to add repos since both have same (422 unprocessable)
   3. edit composite2 and replace 7Server w/ 6Server, publish, promote
   4. try to edit composite by adding composite2-v2.0
   Results: 2 repos displayed for composite2 but only one repo in the add/remove page
   http://www.awesomescreenshot.com/image/1041286/a4ce7a08970bde8c3e5dd9ab033e0382
   http://www.awesomescreenshot.com/image/1041287/c8ac6105f6f9231d7466513a7bf161dc
   http://www.awesomescreenshot.com/image/1041295/f320f768a6c9791a4a581717e307c700

Comment 1 Bryan Kearney 2016-07-26 19:02:58 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Brad Buckingham 2016-08-25 18:01:38 UTC
Unable to reproduce this on Satellite 6.2 GA; therefore, closing.


Note You need to log in before you can comment on or make changes to this bug.