1247621 – Content views showing up twice right after editing CCV

Bug 1247621 - Content views showing up twice right after editing CCV

Summary: Content views showing up twice right after editing CCV

Keywords:
Status:	CLOSED DUPLICATE of bug 1250716
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	WebUI
Sub Component:
Version:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	Unspecified
Assignee:	Ohad Levy
QA Contact:	Katello QA List
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-07-28 12:53 UTC by Maxim Burgerhout
Modified:	2015-08-24 19:56 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-08-24 19:56:12 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
Screenshot demonstrating issue (138.05 KB, image/png) 2015-07-28 12:55 UTC, Maxim Burgerhout	no flags	Details
View All

Description Maxim Burgerhout 2015-07-28 12:53:24 UTC

Description of problem:
When creating a composite content view, all 'component' content views show up twice on the 'Add' tab.

Version-Release number of selected component (if applicable):
6.1.0 beta
foreman-1.7.2.32-1.el7sat.noarch

How reproducible:

Steps to Reproduce:
1. Create CVs, create CCV
2. Select CVs to add to CCV
3. Click 'Add Content Views'

Actual results:
'Add' tab shows, with all available CVs listed twice

Expected results:
'Add' tab will show, and the recently added CVs will no longer be on there

Additional info:
See screenshot.

Comment 1 Maxim Burgerhout 2015-07-28 12:55:57 UTC

Created attachment 1057027 [details]
Screenshot demonstrating issue

Screenshot showing the 'Add' tab right after adding a couple of CV's to the CCV. All listed CVs that are not CCVs show up twice: cv_os_rhel6_x86_64, cv_os_rhel7_x86_64 and cv_pup_generic.

Comment 2 Brad Buckingham 2015-08-24 19:56:12 UTC


*** This bug has been marked as a duplicate of bug 1250716 ***

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