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.
Description of problem: When publishing version 2.0 of a content view, the reindexing process hangs during:
Action:
Actions::ElasticSearch::Repository::IndexContent
State: running
Input:
{"id"=>1278,
"remote_user"=>"USER",
"remote_cp_user"=>"CP_USER",
"locale"=>"en"}
Output:
{}
Action:
Actions::ElasticSearch::Repository::IndexContent
State: running
Input:
{"id"=>1298,
"remote_user"=>"USER",
"remote_cp_user"=>"CP_USER",
"locale"=>"en"}
Output:
{}
Action:
Actions::ElasticSearch::Repository::IndexContent
State: running
Input:
{"id"=>1312,
"remote_user"=>"USER",
"remote_cp_user"=>"CP_USER",
"locale"=>"en"}
Output:
{}
Version-Release number of selected component (if applicable): 2.6.0.20-1
How reproducible: Unable to reproduce this behavior internally, however the case attached to this bugzilla can reproduce this behavior every time.
Steps to Reproduce:
1. Create custom repository and upload packages directly to Satellite
2. Include this repo in a Content View
3. Publish Content View; first version is successful
4. Publish new version of content view
Actual results: Publishing of version 2.0 Content View hangs.
Expected results: Version 2.0 should publish without issue.
Additional info: Specific packages have been attached to the case for testing, if needed.
Description of problem: When publishing version 2.0 of a content view, the reindexing process hangs during: Action: Actions::ElasticSearch::Repository::IndexContent State: running Input: {"id"=>1278, "remote_user"=>"USER", "remote_cp_user"=>"CP_USER", "locale"=>"en"} Output: {} Action: Actions::ElasticSearch::Repository::IndexContent State: running Input: {"id"=>1298, "remote_user"=>"USER", "remote_cp_user"=>"CP_USER", "locale"=>"en"} Output: {} Action: Actions::ElasticSearch::Repository::IndexContent State: running Input: {"id"=>1312, "remote_user"=>"USER", "remote_cp_user"=>"CP_USER", "locale"=>"en"} Output: {} Version-Release number of selected component (if applicable): 2.6.0.20-1 How reproducible: Unable to reproduce this behavior internally, however the case attached to this bugzilla can reproduce this behavior every time. Steps to Reproduce: 1. Create custom repository and upload packages directly to Satellite 2. Include this repo in a Content View 3. Publish Content View; first version is successful 4. Publish new version of content view Actual results: Publishing of version 2.0 Content View hangs. Expected results: Version 2.0 should publish without issue. Additional info: Specific packages have been attached to the case for testing, if needed.