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 1597340 - restrict_composite_view flag prevents CCV promotion even when component versions have been promoted
Summary: restrict_composite_view flag prevents CCV promotion even when component versi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: Samir Jha
QA Contact: Mirek Długosz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-02 16:01 UTC by wclark
Modified: 2021-09-09 14:51 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-katello-3.7.0.12-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:34:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24273 0 None None None 2018-07-17 13:00:04 UTC

Description wclark 2018-07-02 16:01:50 UTC
Description of problem:

The restrict_composite_view flag is preventing CCV versions from being promoted even when all component CV versions have already been promoted to the target environment.

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

Reproduced on 6.3.1
Attempting to reproduce on 6.3.2 as well, but hitting an issue with the 'add_export_distributor' portion of the upgrade currently. I will update the BZ if/when I can reproduce on 6.3.2.

How reproducible:

Easy

Steps to Reproduce:
1. Create a CCV
2. Promote all component CV versions to an LCE
3. Observe that the CCV cannot be promoted to the same LCE when 'restrict_composite_view' is set to True

Actual results:

500 Internal Server Error

Expected results:

CCV Promotes without error

Additional info:

Disabling 'restrict_composite_view' allows the CCV to promote, but it should be able to promote even with 'restrict_composite_view' enabled when the component CVs have been promoted to the target LCE.

Comment 2 wclark 2018-07-02 22:14:25 UTC
I have now reproduced the issue on Satellite 6.3.2.

Comment 7 Samir Jha 2018-07-17 13:00:00 UTC
Created redmine issue http://projects.theforeman.org/issues/24273 from this bug

Comment 8 Satellite Program 2018-07-27 16:21:43 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24273 has been resolved.

Comment 10 Mirek Długosz 2018-08-31 12:20:17 UTC
Issue could not be reproduced on latest Sat 6.4 snap.

When restrict_composite_view flag is set to true:
- it is possible to promote CCV to LCE where component CVs are already available
- it is not possible to promote CCV to LCE where component CVs are not yet available - error message directing user to flag is displayed

Tested on Satellite 6.4.0 snap 19.0 (tfm-rubygem-katello-3.7.0.17-1.el7sat.noarch) using web UI.

Comment 11 Bryan Kearney 2018-10-16 19:34:24 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:2927


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