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.
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"
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.
(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.
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.
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.
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"