Hey,
Not sure where to report LAVA bugs, https://wiki.linaro.org/LAVA (https://wiki.linaro.org/LAVA) indicates I should use the Linaro bugzilla but it seems to be closed? Anyway, I think there's an issue with the CSV result export in LAVA 2018.2, can anyone confirm?
Example CSV: https://validation.linaro.org/results/1686046/csv (https://validation.linaro.org/results/1686046/csv)
The first line of the CSV file is:
[u'job', u'suite', u'result', u'measurement', u'unit', u'duration', u'timeout', u'logged', u'level', u'metadata', u'url', u'name', u'id']1686046,12_bootchart-stop,pass,None,,,,2018-02-28 05:01:35.935783+00:00,,"{'case': 'generate-bootchart-graphic', 'definition': '12_bootchart-stop', 'result': 'pass'}",/results/testcase/2871860,generate-bootchart-graphic,2871860
.. when it probably should've been two lines:
job,suite,result,measurement,unit,duration,timeout,logged,level,metadata,url,name,id
1686046,12_bootchart-stop,pass,None,,,,2018-02-28 05:01:35.935783+00:00,,"{'case': 'generate-bootchart-graphic', 'definition': '12_bootchart-stop', 'result': 'pass'}",/results/testcase/2871860,generate-bootchart-graphic,2871860
I believe the issue is 1) a missing linebreak after the header-line and 2) the formatting of the header line (drop the Python repr stuff).
I have the same problem trying to login to admin on localhost. For me it's
independent of browser and browser cookie configuration. I assume it's an
issue with Django configuration.
Regards
Bill
--
EMEA Field Engineering
Linaro Ltd
Harston Mill CB22 7GG
Cambridge UK
+44 7833 498336 <+44%207833%20498336>
Good morning everyone,
I would like to show you the following :
Did anyone encounter that error in the past while trying to log into a
local standalone master instance of lava ?
I installed LAVA 2018 and the localhost page in being opened without
issues. Things get worst when I try to login.
I am getting that error on chromium and Firefox. Both of them have cookies
enabled.
Best regards,
Good morning everyone,
I am getting in touch with you in order to show you an issue i am facing
after submitting a basic Test Job Definition through my LAVA web page
(localhost). I am a new LAVA user.
After submitting my job, I see the following error in the job's page :
Something seems to be going wrong with "commands" and I am trying to figure
out what it is.
Did anyone already encountered this error in the past?
(I edited a jinja2 device type file and a jinja2 dictionary file as well to
match my device's properties. The device type file is saved in
/etc/lava-server/dispatcher-config/device-types/ and the device dictionary
file is saved in /etc/lava-server/dispatcher-config/devices/).
Thank you for your help,
Hi,
I have an impression that we can have test image "dummy" deployed once I am
sure the image in the device is bootable.
That will save time for downloading and flashing to the device.
Does it still be supported in LAVA v2?
Thanks,
Arthur
Hermanth,
You were able to install on stretch?
I was attempting to do so, but the python3-django-auth-ldap package
wasn't available on anything but sid.
Did you run into the same issue?
Regards,
Chris
> Date: Tue, 27 Feb 2018 14:10:46 +0530
> From: Hemanth K V <kv.hemanth.mys(a)gmail.com>
> To: Lava Users Mailman list <lava-users(a)lists.linaro.org>
> Subject: [Lava-users] set up issue
> Message-ID:
> <CAEua01SDZE6=7+rgnr6+1WA-j3Z3g2ECywP0qtT0xR8Z9GE9Gw(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Lava-Users,
>
> After following the setup of LAVA on Debian 9 stretch and when we try to
> login from UI we face the following error Ref
> https://validation.linaro.org/static/docs/v2/installing_on_debian.html
>
> $ sudo apt install postgresql
> $ sudo apt install lava-server
>
> If the default Apache configuration from LAVA is suitable, you can enable
> it immediately:
>
> $ sudo a2dissite 000-default
> $ sudo a2enmod proxy
> $ sudo a2enmod proxy_http
> $ sudo a2ensite lava-server.conf
> $ sudo service apache2 restart
>
> Forbidden (403)
>
> CSRF verification failed. Request aborted.
>
> You are seeing this message because this site requires a CSRF cookie when
> submitting forms. This cookie is required for security reasons, to ensure
> that your browser is not being hijacked by third parties.
>
> If you have configured your browser to disable cookies, please re-enable
> them, at least for this site, or for 'same-origin' requests.
>
>
> Is there anything missing from the setup.
>
>
> Thanks,
>
> Hemanth.
Hi all,
Why I can't receive the email when I use the 'User notifications' in LAVA ?
notify:
criteria:
status: canceled
verbosity: quiet
recipients:
- to:
method: email
email: hongyu.xu(a)hxt-semitech.com<mailto:hongyu.xu@hxt-semitech.com>
or
notify:
criteria:
status: complete
verbosity: quiet
recipients:
- to:
user: '1680141'
method: email
[cid:image001.png@01D3AFE4.37D7A500]
Best Regards
XuHongyu
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
This is a django configuration issue. I don’t understand why this case (it is very common, obviously) is not handled in the LAVA documentation explicitly. There is a short hint, though, here:
https://validation.linaro.org/static/docs/v2/pipeline-debug.html#using-loca…
You have to add these two variables to /etc/lava-server/settings.conf:
"CSRF_COOKIE_SECURE": false,
"SESSION_COOKIE_SECURE": false
I achieved this using the following commands:
sudo apt-get install jq
jq '.CSRF_COOKIE_SECURE=false | .SESSION_COOKIE_SECURE=false' /etc/lava-server/settings.conf > /tmp/settings.conf && mv /tmp/settings.conf /etc/lava-server/settings.conf
sudo chown root:root /etc/lava-server/settings.conf
sudo service lava-server-gunicorn restart
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(a)garz-fricke.com
www.garz-fricke.com
SOLUTIONS THAT COMPLETE!
Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz
Hello Lava-Users,
After following the setup of LAVA on Debian 9 stretch and when we try to
login from UI we face the following error Ref
https://validation.linaro.org/static/docs/v2/installing_on_debian.html
$ sudo apt install postgresql
$ sudo apt install lava-server
If the default Apache configuration from LAVA is suitable, you can enable
it immediately:
$ sudo a2dissite 000-default
$ sudo a2enmod proxy
$ sudo a2enmod proxy_http
$ sudo a2ensite lava-server.conf
$ sudo service apache2 restart
Forbidden (403)
CSRF verification failed. Request aborted.
You are seeing this message because this site requires a CSRF cookie when
submitting forms. This cookie is required for security reasons, to ensure
that your browser is not being hijacked by third parties.
If you have configured your browser to disable cookies, please re-enable
them, at least for this site, or for 'same-origin' requests.
Is there anything missing from the setup.
Thanks,
Hemanth.
Hello Lava Users,
Trying to setup the x86 based board to our local lava farm to execute tests.
Want to boot the target with pxe based mechanism .Trying to follow the
job definition https://staging.validation.linaro.org/scheduler/job/210084/definition
.With this facing the following error when running the job.Let me know
if i am missing anything with job defination or device defination .
File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py",
line 563, in validate
self.internal_pipeline.validate_actions()
File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py",
line 201, in validate_actions
action.validate()
File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/boot/ipxe.py",
line 221, in validate
elif self.parameters['commands'] not in
device_methods[self.parameters['method']]:
TypeError: unhashable type: 'list'
Device dictionary defination is
Device dictionary yaml:
connection_command: telnet localhost 8021
extends: x86.jinja2
Thanks,
Hemanth.