Bug 1404876 - Pulp celery worker crash on syncing ostree repos
Summary: Pulp celery worker crash on syncing ostree repos
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-14 22:50 UTC by Partha Aji
Modified: 2021-04-06 17:53 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:05:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18308 0 Normal New Pulp celery worker crash on syncing ostree repos 2021-01-19 18:14:42 UTC
Pulp Redmine 2552 0 Normal CLOSED - CURRENTRELEASE updating ostree rpm gives error on sync: LibError: GLib.Error('No such file or directory', 'g-io-error-quark', 1) 2017-04-12 14:34:17 UTC
Red Hat Knowledge Base (Solution) 2972961 0 None None None 2017-03-17 21:25:58 UTC

Description Partha Aji 2016-12-14 22:50:24 UTC 
On a Satellite that has ostree enabled, enable and sync the RH Atomic Tree.
Some customers have reported the following error.

Dec 14 20:25:01 satellite celery: OSTree:ERROR:src/libostree/ostree-repo-static-delta-processing.c:691:dispatch_open: assertion failed: (repo->mode == OSTREE_REPO_MODE_BARE || repo->mode == OSTREE_REPO_MODE_BARE_USER)
Dec 14 20:25:01 satellite pulp: celery.worker.job:ERROR: (1169-66976) Task pulp.server.managers.repo.sync.sync[2eee94d5-994a-48b1-96db-88fd64760d8f] raised unexpected: WorkerLostError('Worker exited prematurely: signal 6 (SIGIOT).',)


Workaround:

Error similar to this have been fixed in the ostree upstream
 (https://github.com/ostreedev/ostree/issues/407 and https://github.com/ostreedev/ostree/pull/408) 

Work around might be to upgrade their ostree rpm to a later version (ostree-2016.10-1.atomic.el7 and above.)
Comment 3 Tom McKay 2017-01-30 19:34:54 UTC 
Created redmine issue http://projects.theforeman.org/issues/18308 from this bug
Comment 4 pulp-infra@redhat.com 2017-01-30 20:01:19 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2017-01-30 20:01:22 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2017-01-31 16:31:12 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2017-02-13 15:01:24 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2017-02-15 15:02:15 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 9 Jeff Ortel 2017-02-15 15:46:38 UTC 
The PR (commit) referenced in the pulp redmine issue needs to be cherry picked downstream.  Also, note there is a foreman issue that also needs to be completed as part of the solution.
Comment 10 Partha Aji 2017-02-15 16:04:35 UTC 
Need to add a foreman-rake task "repair corrupted syncs" caused by this issue.
Comment 12 Dennis Kliban 2017-03-14 02:25:50 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 15 Pavel Moravec 2017-03-17 21:16:21 UTC 
Updating ostree to 2016.15 or 2017.1 prevents the segfault - at least for the 01798096 case.
Comment 18 pulp-infra@redhat.com 2017-04-12 14:34:18 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 20 Satellite Program 2017-10-27 22:10:54 UTC 
Upstream bug assigned to paji
Comment 21 Bryan Kearney 2018-09-04 18:05:49 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.