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 :
?
Regards,
Le 2 mars 2018 05:47, "Magnus Olsson" magnus@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@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,
Hi Conrad,
On Friday 02 March 2018 10:43 AM, Conrad Djedjebi wrote:
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 :
You must have this configuration if you are running a non HTTPS instance https://staging.validation.linaro.org/static/docs/v2/pipeline-debug.html#usi...
HTH. Thank You.
Hi Conrad,
As Magnus pointed out, you need to change/add the two variables in /etc/lava-server/settings.conf
"CSRF_COOKIE_SECURE": false, "SESSION_COOKIE_SECURE": false
and then restart the lava-server-gunicorn process.
The whole process is described at the very end of the page here: https://validation.linaro.org/static/docs/v2/pipeline-debug.html#using-local...
HTH,
On 03/02/2018 06:13 AM, Conrad Djedjebi wrote:
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 :
?
Regards,
Le 2 mars 2018 05:47, "Magnus Olsson" <magnus@minimum.se mailto:magnus@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 <https://projects.linaro.org/browse/LAVA-1253>) On Mar 1, 2018 22:49, Conrad Djedjebi <conrad.djedjebi@linaro.org <mailto:conrad.djedjebi@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,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi Magnus, Senthil, Stevan,
I am running a non https instance indeed. I changed CSRF_COOKIE_SECURE and SESSION_COOKIE_SECURE variables and the issue was resolved.
Thank you all for your responses,
regards,
On 2 March 2018 at 07:54, Stevan Radakovic stevan.radakovic@linaro.org wrote:
Hi Conrad,
As Magnus pointed out, you need to change/add the two variables in /etc/lava-server/settings.conf
"CSRF_COOKIE_SECURE": false, "SESSION_COOKIE_SECURE": false
and then restart the lava-server-gunicorn process.
The whole process is described at the very end of the page here: https://validation.linaro.org/static/docs/v2/pipeline-debug. html#using-localhost-or-non-https-instance-url
HTH,
On 03/02/2018 06:13 AM, Conrad Djedjebi wrote:
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 :
?
Regards,
Le 2 mars 2018 05:47, "Magnus Olsson" magnus@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@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,
Lava-users mailing listLava-users@lists.linaro.orghttps://lists.linaro.org/mailman/listinfo/lava-users
-- Stevan Radaković | LAVA Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
lava-users@lists.lavasoftware.org
-
Conrad Djedjebi -
Senthil Kumaran S -
Stevan Radakovic