Better checking/messaging of --exec script problems
Bug #292733 reported by
Eric Hammond
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| vm-builder (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
If the exec script is missing the following error is given at the start of the run:
The path to the --execscript file is invalid: SCRIPTNAME. Make sure you are providing a full path.
It might be nice to also check to see if the script is executable and provide a helpful message to that effect. The current behavior if the script isn't executable is to spend the time building the image and then at the end die with a stack trace ending with the slightly unintuitive error message:
OSError: [Errno 13] Permission denied
Revision history for this message
| Chuck Short (zulcss) wrote | #1 |
| Changed in vm-builder (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
To post a comment you must log in.
Thanks for the bug report, I agree if the script doesnt exist then it show an error.
Regards
chuck