Hide Forgot
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.
Moving 6.2 bugs out to sat-backlog.
This looks due to elasticsearch which is removed in 6.2. Can the CU test this on 6.2?
I think the component of this should probably not be "Pulp". Brad, if you agree, can you perhaps find a better component for it?
I'm changing the component since this does not appear to be a Pulp bug, based on available info.