lpcraft failed with internal error despite successful execution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lpci |
Fix Released
|
Low
|
Jürgen Gmach |
Bug Description
Despite successfully completing the given build and creating the output folder structure, lpcraft returned a non-zero return code due to a CalledProcessError while running `lxc exec readlink -f -z --`. The output artifacts were not copied out of the container.
If logs are to be believed, this is caused by a race between the return from the incomplete `lxc exec` and the call to `lxc stop` - note the call to `lxc exec` at 14:31:42.345, the call to `lxc stop` at 14:31:42.533, and the error at 14:31:44.086:
2022-03-02 14:31:42.037 Executing in container: lxc --project lpcraft exec local:lpcraft-
2022-03-02 14:31:42.208 Executing in container: lxc --project lpcraft exec local:lpcraft-
2022-03-02 14:31:42.345 Executing in container: lxc --project lpcraft exec local:lpcraft-
2022-03-02 14:31:42.461 Executing on host: lxc --project lpcraft config device show local:lpcraft-
2022-03-02 14:31:42.533 Executing on host: lxc --project lpcraft stop local:lpcraft-
2022-03-02 14:31:44.086 lpcraft internal error: CalledProcessEr
2022-03-02 14:31:44.089 Traceback (most recent call last):
...<snipped>
Full log attached for details.
Related branches
- Colin Watson (community): Approve
-
Diff: 98 lines (+58/-6)3 files modifiedNEWS.rst (+3/-0)
lpcraft/commands/run.py (+8/-6)
lpcraft/commands/tests/test_run.py (+47/-0)
Changed in lpcraft: | |
status: | Triaged → Fix Committed |
assignee: | nobody → Jürgen Gmach (jugmac00) |
This bug appears to be a consequence of there being no files located in the expected output location. So it is not a race after all but perhaps just could use some helpful error text