Bug 1499826

Summary: UI shows another versions to add after adding same component view's version in composite content view.
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, nkathole, walden
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 14:49:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of UI none

Description Nikhil Kathole 2017-10-09 12:52:09 UTC
Created attachment 1336388 [details]
screenshot of UI

Description of problem: A composite content view should not have 2 versions of the same component view. But when we tried to add 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create one content view and publish it twice (we have two versions)

# hammer content-view info --id=6
ID:                     6
Name:                   test_view
Label:                  test_view
Composite:              false
Description:
Content Host Count:     0
Organization:           Default Organization
Yum Repositories:
 1) ID:    5
    Name:  sat6tool6
    Label: sat6tool6
Docker Repositories:

OSTree Repositories:

Puppet Modules:

Lifecycle Environments:
 1) ID:   2
    Name: DEV
 2) ID:   1
    Name: Library
Versions:
 1) ID:        7
    Version:   1.0
    Published: 2017/10/09 12:02:37
 2) ID:        8
    Version:   2.0
    Published: 2017/10/09 12:03:50
Components:

Activation Keys:

2. Create a composite content view with one of the content view version as components

# hammer --output=csv content-view create --composite --organization-id="1" --name="composite_CV" --component-ids=
"7"
Message,Id,Name
Content view created,8,composite_CV

3. Now in UI, navigate to Content -> content view -> composite_CV 
4. Click on content views tab
5. Click on add tab

Actual results:
You can see another version of same CV to add.

Expected results:
Add tab should not list CV if one of the version is already added.

Additional info:
Though it list another version from same CV to add, we can't add it to composite CV.It shows error as "An error occurred updating the Content View: is invalid"

Comment 2 Walden Raines 2017-10-17 14:49:03 UTC
Are you able to reproduce this if you do the same in the UI only?  I cannot reproduce this using the UI which leads me to believe that the problem may be in hammer.  I.E. perhaps the content view wasn't really added to the composite in step 2 above.

Comment 3 Nikhil Kathole 2017-10-17 15:47:39 UTC
(In reply to Walden Raines from comment #2)
> Are you able to reproduce this if you do the same in the UI only?  I cannot
> reproduce this using the UI which leads me to believe that the problem may
> be in hammer.  I.E. perhaps the content view wasn't really added to the
> composite in step 2 above.

I found it is reproducible using hammer...tried step 1 and 2 with UI but can't found same behaviour.

Comment 4 Bryan Kearney 2018-11-01 14:43:20 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is  not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 5 Bryan Kearney 2018-11-30 14:49:06 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.