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 1740718 - HTTP 500 Response on Incremental Update
Summary: HTTP 500 Response on Incremental Update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Jonathon Turel
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-13 14:35 UTC by Lai
Modified: 2019-10-22 19:50 UTC (History)
1 user (show)

Fixed In Version: tfm-rubygem-katello-3.12.0.16-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:50:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27612 0 Normal Closed Incremental update broken for puppet modules 2020-05-07 15:18:57 UTC

Description Lai 2019-08-13 14:35:19 UTC 
Description of problem:
HTTP 500 server error when calling the incremental update.

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

How reproducible:
Always

Steps to Reproduce:
This is found in automation with the following steps:
1. Create and publish CV with some content
2. Create composite CV, add previously created CV inside it
3. Publish composite CV
4. Create a puppet repo and upload a puppet module into it
5. Incrementally update the CVV with the puppet module with 'propagate_all_composites' flag set to 'True'

Actual results:
Successful API call.

Expected results:
HTTP 500 to server
Comment 6 Jonathon Turel 2019-08-13 17:46:23 UTC 
Created redmine issue https://projects.theforeman.org/issues/27612 from this bug
Comment 7 Bryan Kearney 2019-08-13 18:01:11 UTC 
Upstream bug assigned to jturel
Comment 8 Bryan Kearney 2019-08-13 18:01:12 UTC 
Upstream bug assigned to jturel
Comment 11 Bryan Kearney 2019-08-20 16:01:15 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27612 has been resolved.
Comment 13 Lai 2019-08-23 19:04:27 UTC 
Steps to test:
This is found in automation with the following steps:
1. Create and publish CV with some content
2. Create composite CV, add previously created CV inside it
3. Publish composite CV
4. Create a puppet repo and upload a puppet module into it
5. Incrementally update the CVV with the puppet module with 'propagate_all_composites' flag set to 'True'

Actual results:
Successful API call.

Expected results:
Successful API call.

Done via automation and passes.

Tested on 6.6.0 Snap 17

Marking issue as verified.
Comment 14 Bryan Kearney 2019-10-22 19:50:57 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.