| Summary: | Permission denied problems when running Hudson builds | ||
|---|---|---|---|
| Product: | Community | Reporter: | Alexander Igdalov <alexander.igdalov> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d_a_carver, ed |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Alexander Igdalov
On your build, please make sure you have configured it to run only on the Master node. You may be running into issues where it is trying to go over to one of the slaves and the slaves aren't yet setup with everything we need. (In reply to comment #1) > On your build, please make sure you have configured it to run only on the > Master node. You may be running into issues where it is trying to go over to > one of the slaves and the slaves aren't yet setup with everything we need. Hi David, Tying to Master node helps, thanks. I am decreasing priority and severity since then. BTW, back to ln problem, do you know why it doesn't work and whether any improvements about it are expected? (In reply to comment #2) > (In reply to comment #1) > > On your build, please make sure you have configured it to run only on the > > Master node. You may be running into issues where it is trying to go over to > > one of the slaves and the slaves aren't yet setup with everything we need. > > Hi David, > > Tying to Master node helps, thanks. I am decreasing priority and severity since > then. BTW, back to ln problem, do you know why it doesn't work and whether any > improvements about it are expected? Not sure...it seems to be specific to the main build machine. I'm running the same version of Hudson locally under Ubuntu and don't see the issue. It is best to use the RESTful links anyways, especially with the slave machines coming on line. Thanks, Dave. I am closing the bug. |