Bug 673174
| Summary: | error: unpacking of archive failed: cpio: lstat failed - Resource temporarily unavailable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> | ||||
| Component: | eclipse-mylyn | Assignee: | Chris Aniszczyk <zx> | ||||
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0 | CC: | borgan, mnowak, overholt, patrickm, syeghiay, szhou | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | eclipse-mylyn-3_4_2-9_el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-19 11:43:32 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 670159 | ||||||
| Attachments: |
|
||||||
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Chris, could you please specify why do you think that the problem is in cpio? Alex, is there strace available? The error is in install.log, which is from yum, so this is most likely an rpm bug. So ... let's try rpm guys ;) (In reply to comment #3) > Alex, is there strace available? You can find all available logs in comment #1 but looking at them I don't see anything that tells me something is wrong. lstat() returning EAGAIN? Oh well, there's first time for everything... Too bad it's not saying anything about the failing file :-/ A strace log (with -elstat to limit the noise) would be helpful. AFAICS there are network filesystems involved apart from the install method being nfs, unless some package is doing funky tricks in %post. It'd be interesting to know whether this is reproducable with non-nfs installation, and when did this error start occurring (eg is this reproducable with RHEL 6.0.0). Actually ignore the above, no need for further information as I'm able to reproduce this locally with just 'yum install eclipse-mylyn' to a chroot from rhel6 repository. Okay, the EAGAIN looks like it's "leaked" from somewhere (yum callback possibly), installing directly with rpm gives ENOTDIR which leads to the smoking gun:
eclipse-mylyn is trying to install stuff into %{_libdir}/eclipse/eclipse/dropins but %{_libdir}/eclipse/eclipse is a regular file from eclipse-platform package. I'm not at all familiar with eclipse tree structure but I'd suppose eclipse-mylyn should be putting its files into %{_libdir}/eclipse/dropins/ instead.
So apart from the error message being misleading and obscure, this is a packaging bug.
Chris, what do you think about comment #9? Looks reasonable to me. Can we have a new spin to 6.1 erratum, please? Investigating. In the spec file we set...
%global install_loc %{_datadir}/eclipse/dropins
Then when we install..
%install
rm -rf %{buildroot}
install -d -m 755 $RPM_BUILD_ROOT%{_datadir}/eclipse
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn-java
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn-pde
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn-trac
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn-webtasks
install -d -m 755 $RPM_BUILD_ROOT%{install_loc}/mylyn-wikitext
Looks like we are doing the right thing?
Andrew, do you have some thoughts here?
Is it possible that install_loc being leaked from some other RPM in the transaction? It fails even when installing mylyn* packages only. I will commit the following fix once I get the acks:
diff -u -r1.24 eclipse-mylyn.spec
--- eclipse-mylyn.spec 17 Jan 2011 18:09:05 -0000 1.24
+++ eclipse-mylyn.spec 3 Feb 2011 15:19:54 -0000
@@ -3,7 +3,7 @@
%endif
%global eclipse_base %{_libdir}/eclipse
-%global install_loc %{eclipse_base}/eclipse/dropins
+%global install_loc %{eclipse_base}/dropins
# Taken from update site so we match upstream
# http://download.eclipse.org/tools/mylyn/update/e3.5/
%global qualifier v20100916-0100-e3x
Fixed in eclipse-mylyn-3_4_2-9_el6 https://brewweb.devel.redhat.com/brew/taskinfo?taskID=3085572 *** Bug 676233 has been marked as a duplicate of this bug. *** An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0568.html |
Created attachment 475633 [details] screenshot Description of problem: During installation I get this error in install.log: Installing eclipse-mylyn-3.4.2-8.el6.x86_64 error: unpacking of archive failed: cpio: lstat failed - Resource temporarily unavailable Resource temporarily unavailable sounds like a networking issue but IIRC anaconda should be able to retry the download. Filing against anaconda to get more visibility to this issue. Version-Release number of selected component (if applicable): anaconda-13.21.91 How reproducible: always Steps to Reproduce: 1. Perform install with %packages * -@conflicts-<variant> 2. 3. Actual results: When at 2133 of 2756 packages I get an error that eclipse-mylyn package can't be installed (see screenshot). The error above in in install.log. Expected results: Additional info: