Hi Admirer,

I had the similar problem and we have a patch in place to fix this issue. https://git.lavasoftware.org/lava/lava/-/merge_requests/959

The patch will be available in the official 2020.02 release which current ETA is in 2 days. I'll amend the docker-compose README after the release is out but in a nutshell you'll be able to add 'dispatcher_tftp_ip' and 'dispatcher_nfs_ip' in the dispatcher.yaml which will be then used by the u-boot setenv commands.

Regards, Stevan

On 2/24/20 8:48 AM, admirer mishra wrote:

Hi Stevan,

I am using latest lava-docker containers 2020.01 so using rest api I set the dispatcher ip and post it, which creates a dispatcher.yaml file with the content dispatcher_ip: '141.64.81.191' (not my ip)

I checked it's there in the directory (/etc/lava-server/dispatcher.d/lava-dispatcher/dispatcher.yaml), but still no change in SERVER_IP or NFS_SERVER_IP (everything is same) while running the job, due to which not able to do tftp. I even tried with restarting the lava-server but still no change.

Thanks for your time.

regards, admirer mishra

---

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users