Bug 1317651 - [abrt] failure of bug reporting
Summary: [abrt] failure of bug reporting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: retrace-server
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 18:28 UTC by Joachim Frieben
Modified: 2016-03-29 07:19 UTC (History)
7 users (show)

Fixed In Version: retrace-server-1.15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-29 07:19:45 UTC
Type: Bug


Attachments (Terms of Use)

Description Joachim Frieben 2016-03-14 18:28:35 UTC
Description of problem:
Bug reporting to the retrace server currently fails for current Fedora 24. The bug reporting tool returns the error message:

----
INFO: mock.py version 1.2.15 starting (python version = 2.7.5)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
Start: clean chroot
Finish: clean chroot
Start: chroot init
INFO: calling preinit hooks
Mock Version: 1.2.15
INFO: Mock Version: 1.2.15
Start: yum install
ERROR: Command failed. See logs for output.
 # /usr/bin/yum --installroot /var/lib/mock/990571608/root/ --skip-broken instal
l bash cpio glibc-debuginfo abrt-addon-ccpp shadow-utils gdb rpm --setopt=tsflag
s=nocontexts
WARNING: unable to delete selinux filesystems (/tmp/mock-selinux-plugin.RTQi3G):
 [Errno 1] Operation not permitted: '/tmp/mock-selinux-plugin.RTQi3G'
---

Version-Release number of selected component (if applicable):
abrt-2.8.0-4.fc24

How reproducible:
Always

Steps to Reproduce:
1. Report ABRT issue to retrace server.

Actual results:
Bug processing fails

Expected results:
Bug processing succeeds

Additional info:
Issue absent when reporting issues for current Fedora 23.

Comment 1 Jakub Filak 2016-03-15 08:57:15 UTC
I've opened the following upstream pull-request:
https://github.com/abrt/retrace-server/pull/110

Comment 2 Mike McCune 2016-03-28 21:59:03 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Jakub Filak 2016-03-29 07:19:45 UTC
This issue should be fixed now. Please, feel free to reopen if needed.


Note You need to log in before you can comment on or make changes to this bug.