Bug 971494
Summary: | [abrt] mock-1.1.32-1.fc18: subprocess.py:1249:_execute_child:OSError: [Errno 2] No such file or directory | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eric Harney <eharney> | ||||||||
Component: | mock | Assignee: | Clark Williams <williams> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 18 | CC: | eharney, mebrown, williams | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:e30e45bdabaef8e665478770e800e61aca92d279 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2014-01-04 15:51:31 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Eric Harney
2013-06-06 16:15:53 UTC
Created attachment 757735 [details]
File: backtrace
Created attachment 757736 [details]
File: core_backtrace
Created attachment 757737 [details]
File: environ
Eric, That almost looks like rpm wasn't installed, which doesn't make sense. The error is being thrown from the subprocess.Popen call, where we're running an rpm command to install the source rpm. If rpm started up properly and the srpm didn't exist, we'd get an error from rpm. So the OSError 2, 'No such file or directory' to me means that rpm isn't there. I see that you're using --no-clean, meaning you're running from a pre-existing chroot. Can you verify that the rpm package is installed and intact in the chroot? This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Unfortunately I don't have this environment setup any more, so I can't provide any more info about this particular failure. It's possible that the environment wasn't built correctly or was corrupted. Guessing this was the same issue as bug 957992, which seems to have been an selinux issue. Will close for now and reopen if it pops up again. |