On Mon, 11 Dec 2018 at 11:30, Neil Williams <neil.williams at linaro.org> wrote:
On Tue, 11 Dec 2018 at 11:28, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
Thanks, the CLI operations are very helpful for automating the process. However, the docs say that all devices in "Reserved" state have to have their "current job" cleared. I can use "lava-server manage devices details" to check whether this field is actually set. There is no command to modify it, though. Seems like using the Python API is the only way to go here, right? The same applies to setting "Running" jobs to "Cancelled".
https://git.lavasoftware.org/lava/lava/merge_requests/273
This should get into the upcoming 2018.12 release.
Thank you very much for your quick help. The "lava-server manage jobs fail" command takes care of clearing the "current job" field of the associated device, do I understand that right?
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
On Tue, 11 Dec 2018 at 12:02, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
On Mon, 11 Dec 2018 at 11:30, Neil Williams <neil.williams at linaro.org> wrote:
On Tue, 11 Dec 2018 at 11:28, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
Thanks, the CLI operations are very helpful for automating the process. However, the docs say that all devices in "Reserved" state have to have their "current job" cleared. I can use "lava-server manage devices details" to check whether this field is actually set. There is no command to modify it, though. Seems like using the Python API is the only way to go here, right? The same applies to setting "Running" jobs to "Cancelled".
https://git.lavasoftware.org/lava/lava/merge_requests/273
This should get into the upcoming 2018.12 release.
Thank you very much for your quick help. The "lava-server manage jobs fail" command takes care of clearing the "current job" field of the associated device, do I understand that right?
That was a hangover from V1 scheduling issues. It's not needed any longer, the V2 scheduler sorts out the state.
On Mon, 11 Dec 2018 at 13:21, Neil Williams <neil.williams at linaro.org> wrote:
On Tue, 11 Dec 2018 at 12:02, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
On Mon, 11 Dec 2018 at 11:30, Neil Williams <neil.williams at linaro.org> wrote:
On Tue, 11 Dec 2018 at 11:28, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
Thanks, the CLI operations are very helpful for automating the process. However, the docs say that all devices in "Reserved" state have to have their "current job" cleared. I can use "lava-server manage devices details" to check whether this field is actually set. There is no command to modify it, though. Seems like using the Python API is the only way to go here, right? The same applies to setting "Running" jobs to "Cancelled".
https://git.lavasoftware.org/lava/lava/merge_requests/273
This should get into the upcoming 2018.12 release.
Thank you very much for your quick help. The "lava-server manage jobs fail" command takes care of clearing the "current job" field of the associated device, do I understand that right?
That was a hangover from V1 scheduling issues. It's not needed any longer, the V2 scheduler sorts out the state.
Thanks again for the information.
I have one remark on the documentation change:
https://git.lavasoftware.org/lava/lava/merge_requests/273/diffs?commit_id=70...
The LAVA services must be stopped AFTER the instance check, otherwise "lava-server manage check --deploy" fails:
ERRORS: lava service: lava-logs service is not active. lava service: lava-master service is not active. lava service: lava-publisher service is not active. lava service: lava-server-gunicorn service is not active.
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
On Tue, 11 Dec 2018 at 15:34, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
I have one remark on the documentation change:
https://git.lavasoftware.org/lava/lava/merge_requests/273/diffs?commit_id=70...
The LAVA services must be stopped AFTER the instance check, otherwise "lava-server manage check --deploy" fails:
ERRORS: lava service: lava-logs service is not active. lava service: lava-master service is not active. lava service: lava-publisher service is not active. lava service: lava-server-gunicorn service is not active.
And another note: in the restore sequence, the restoration of test job log files and service log files is missing.
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
On Tue, 11 Dec 2018 at 16:23, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
On Tue, 11 Dec 2018 at 15:34, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
I have one remark on the documentation change:
https://git.lavasoftware.org/lava/lava/merge_requests/273/diffs?commit_id=70...
The LAVA services must be stopped AFTER the instance check, otherwise "lava-server manage check --deploy" fails:
ERRORS: lava service: lava-logs service is not active. lava service: lava-master service is not active. lava service: lava-publisher service is not active. lava service: lava-server-gunicorn service is not active.
Those error messages are predictable and shouldn't be much of an issue. I have updated the doc though.
And another note: in the restore sequence, the restoration of test job log files and service log files is missing.
test job log files, yes. Whether or not to restore service log files is up to local admins to decide. It probably isn't worth doing.
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
lava-users@lists.lavasoftware.org
-
Neil Williams -
Tim Jaacks