| Summary: | Publishing ver 2.0 of Content View including Satellite-hosted repository hangs on indexing content | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Rick Dixon <rdixon> |
| Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.7 | CC: | bbuckingham, bkearney, chrobert, mhrivnak, rdixon |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-05 14:17:42 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: | |
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. |
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.