On 01/28/2013 07:46 AM, Paul Sokolovsky wrote:
Hello,
As far as I can tell, LAVA currently doesn't set hostname of a LAVA
board when running tests, which leads for usage of whatever generic (or
random) value was configured in build image. That may pose problem if
test/build uses hostname for some logging or identification.
I tried to investigate how it happened that lava-dispatcher doesn't try
to set hostname, and actually found it used to, but that was tied to
recognition of test prompts, and once that was refactored, setting
hostname also gone, see
http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revision/402
(grep for "_customize_ubuntu" - it got factored out to another file,
and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as
lava-dispatcher bug, or are there other reasons for not setting a
hostname.
I think this is a reasonable feature request. I think we could easily
add something to the _customize_* functions to set the hostname.
Probably takes less than an hour to implement/test/merge.
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
