Bug 1292556

Summary:	Userspace core support for interactive mode - using existing mock implementation
Product:	[Fedora] Fedora EPEL	Reporter:	Dave Wysochanski <dwysocha>
Component:	retrace-server	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	el6	CC:	bhubbard, ddouwsma, germano, gveitmic, harshula, hokuda, lherbolt, michal.toman, nobody, skito
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 15:08:33 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:
Embargoed:
Bug Depends On:	1320104, 1264005
Bug Blocks:

Description Dave Wysochanski 2015-12-17 18:57:41 UTC

Description of problem:
There seems to be code for this but this has never worked as far as I know. Some people have been working on this, and I think at least POC is worked out, but I'm not sure the limitations or the constraints. For example, will cores from only certain RHELs be supported? Also do we need to run retrace-server on RHEL7 or will our existing retrace-server on RHEL6 be ok? Is there some setup required?

Version-Release number of selected component (if applicable):
retrace-server-1.12-3.el6.noarch

How reproducible:
Every time.

Steps to Reproduce:
Submit a userspace core through the same 'manager' page.

Actual results:
retrace-server does not recognize the type of file or setup the proper libraries and environment to run gdb.

Expected results:
Able to run gdb on the userspace cores with all libraries loaded.

Additional info:
There was some significant code which went upstream in 1.13 so it may already be fixed. Filing this to make sure it works in the latest code, and what the limitations may be.

I think we may need rhel7 base for this retrace-server functionality but I'm not sure.

Also last I looked the existing code uses mock. As has been seen with vmcores, mock has it's limitations / weaknesses such as only one user opening the core and security concerns (and see other retrace-server bugs which mention mock).

There was at least one person attempting to do userspace cores with containers. If there's competing implementations we may need to fork another bug for container implementation, or use this bug if it's feasible in the shorter term.

Comment 2 Harshula Jayasuriya 2015-12-17 23:26:36 UTC

IIRC, there are multiple people working to solve this problem. Could we please have a status update from each? Thanks!

Comment 3 Brad Hubbard 2015-12-18 00:04:19 UTC

I committed to looking into this and I have had a look but need to go much deeper. I hope to get the time to do this soon and will report back in the new year.

Comment 5 Brad Hubbard 2015-12-18 02:27:17 UTC

I suggest we focus on handling mainstream before we even consider corner cases. There will always be corner cases such a 3p libs that we will not be able to get anything meningful from however we may be able to flag the presence of 3p libs due to unresolved or missing build-ids. Crawl before walk, walk before run.

Comment 9 Dave Wysochanski 2016-03-24 12:14:34 UTC

I would consider this another potential blocker, at least a 'nice to have':
https://bugzilla.redhat.com/show_bug.cgi?id=1320104

Today userspace cores require 'reposync' and a copy of all packages on all distro versions where a core can come in.  This is really a huge overhead which seems unnecessary so it would be good if we can just use repos of all packages instead of copies.  The above bug is necessary since today we can only use a single repo AFAIK.

Comment 10 Ben Cotton 2020-11-05 16:53:07 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 11 Ben Cotton 2020-11-05 16:55:44 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 12 Ben Cotton 2020-11-30 15:08:33 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.