| Summary: | Fedora 20 in AB infrastructure: "Resource temporarily unavailable" | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Beth Flanagan <elizabeth.flanagan> |
| Component: | autobuilder | Assignee: | Michael Halstead <mhalstead> |
| Status: | VERIFIED OBSOLETE | QA Contact: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Severity: | normal | ||
| Priority: | Medium | CC: | bogdanx.a.voiculescu, elizabeth.flanagan, infras.ab.watcher, Infras.watcher, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 1.9 | ||
| Hardware: | x86 | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Beth Flanagan
2015-02-25 13:34:52 UTC
I'm pretty sure at this point that this is an issue with the Fedora 20 machine's hardware. 1. We removed f20 from the pool and have not seen this since. 2. I'm running f20 and have never seen these errors. I'm going to kick this over to halstead and see if he has some thoughts. Michael: Any update on whether this was some kind of hardware issue? All hardware tests I ran passed without any trouble and there is nothing in the logs. If you ssh to fedora20.yp you can see a troublesome make (pid 12464) still running from the last failure. Perhaps it can offer clues? At this point I propose we reload the machine with Fedora22 which is due out next week. It doesn't seem this will be looked into more deeply and this machine is currently on standby. Any objections? That sounds fine. Let me know when it's done. It appears the question was answered. Wiped and starting over with Fedora 22. Nothing to be verified. |