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.

Bug 1411074

Summary: Latest cv version is not listed in composite content view while adding new cv into ccv.
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.4CC: bbuckingham, ehelms, jcallaha, oshtaier, vincent.vandecamp
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:37 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:
Bug Depends On: 1177766    
Bug Blocks:    
Attachments:
Description Flags
available version of content view
none
version listed in ccv
none
verification screenshot none

Description Ranjan Kumar 2017-01-08 07:03:27 UTC
Created attachment 1238320 [details]
available version of content view

Description of problem:
When adding new content view into composite content view and if the content view is having only one published version(suppose 5.0) it display incorrect version(1.0) of content view. 

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

How reproducible:
Always

Steps to Reproduce:
1. Create content view called cv1.
2  publish 2 versions of the cv1.
3. Now delete the version 1.0 of cv1.
4. Create a composite content view ccv1.
5. Go to ccv1 -> content view -> Add, it display version 1.0 for cv1

Actual results:
The versions are incorrect

Expected results:
The versions should be the latest

Additional info:
Attached is a screen shot of the issue.

Comment 1 Ranjan Kumar 2017-01-08 07:04:47 UTC
Created attachment 1238321 [details]
version listed in ccv

Comment 3 Brad Buckingham 2017-01-10 22:55:19 UTC
The issue described by this bugzilla has been addressed in the upstream and will be included as part of the solution to bug 1177766.  Due to the complexity of that solution, it will not be available until Satellite 6.3.

Comment 4 jcallaha 2018-01-29 18:35:34 UTC
Verified in Satellite 6.3 Snap 33.

Followed the verification steps in the original report. After creating the CCV, I see just the 2.0 version, as expected.

See verification screenshot.

Comment 5 jcallaha 2018-01-29 18:35:55 UTC
Created attachment 1387946 [details]
verification screenshot

Comment 6 Satellite Program 2018-02-21 16:54:37 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336