non-interactive mode leaves broken dispatcher configuration
Bug #1056428 reported by
Antonio Terceiro
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Deployment Tool |
Fix Released
|
High
|
Antonio Terceiro |
Bug Description
after installing a lava instance, I ended up with dispatcher configuration that had mostly empty variables:
LAVA_SERVER_IP =
# Location for rootfs/boot tarballs extracted from images
LAVA_IMAGE_TMPDIR =
# URL where LAVA_IMAGE_TMPDIR can be accessed remotely
LAVA_IMAGE_URL = http://
# Location on the device for storing test results.
LAVA_RESULT_DIR =
# Location for caching downloaded artifacts such as hwpacks and images
LAVA_CACHEDIR =
# This is the address and port of cache proxy service, format is like:
# LAVA_PROXY = http://
LAVA_PROXY =
the dispatcher configration code sets sensible defaults to most of these, so it should not ke skipped.
Related branches
lp:~terceiro/lava-deployment-tool/fix-1056428
- Linaro Validation Team: Pending requested
-
Diff: 36 lines (+11/-2)1 file modifiedlava-deployment-tool (+11/-2)
Changed in lava-deployment-tool: | |
assignee: | nobody → Antonio Terceiro (terceiro) |
importance: | Undecided → High |
summary: |
- non-interactive mode should not skip dispatcher configuration + non-interactive mode leaves broken dispatcher configuration |
Changed in lava-deployment-tool: | |
status: | New → Fix Committed |
Changed in lava-deployment-tool: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.