Hi Magnus Olsson,
Have you experienced issues regarding CSRF token?
After migrating from LAVA 2016 to LAVA 2018, did your first login into your
server return the following :
Django.png
<https://drive.google.com/a/linaro.org/file/d/0B0v46EqqhhcaVk9zM2N1UHJnM2NXd…>
?
Regards,
Le 2 mars 2018 05:47, "Magnus Olsson" <magnus(a)minimum.se> a écrit :
> We recently upgraded our master from an old 2016.11 to 2018.2. After about
> a week of fixing migration issues things are starting to work again. 2018.2
> is so far a good release, the only open issue we have left is the broken
> csv export that breaks our tools for generating external reports (
> https://projects.linaro.org/browse/LAVA-1253)
>
>
> On Mar 1, 2018 22:49, Conrad Djedjebi <conrad.djedjebi(a)linaro.org> wrote:
> >
> > Good morning LAVA users,
> >
> > I would like to know if there is someone among the LAVA users who
> installed his own LAVA 2018 master instance ?
> >
> > Is everyone here using the LAVA LAB master instance available here :
> https://validation.linaro.org ?
> >
> > Am I the only one who is installing his own LAVA 2018 master instance?
> >
> >
> > Best regards,
We recently upgraded our master from an old 2016.11 to 2018.2. After about a week of fixing migration issues things are starting to work again. 2018.2 is so far a good release, the only open issue we have left is the broken csv export that breaks our tools for generating external reports (https://projects.linaro.org/browse/LAVA-1253)
On Mar 1, 2018 22:49, Conrad Djedjebi <conrad.djedjebi(a)linaro.org> wrote:
>
> Good morning LAVA users,
>
> I would like to know if there is someone among the LAVA users who installed his own LAVA 2018 master instance ?
>
> Is everyone here using the LAVA LAB master instance available here : https://validation.linaro.org ?
>
> Am I the only one who is installing his own LAVA 2018 master instance?
>
>
> Best regards,
Good morning LAVA users,
I would like to know if there is someone among the LAVA users who installed
his own LAVA 2018 master instance ?
Is everyone here using the LAVA LAB master instance available here :
https://validation.linaro.org ?
Am I the only one who is installing his own LAVA 2018 master instance?
Best regards,
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.