Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container. Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djang...
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
Thanks for any help you can provide regarding this matter.
Regards,
Jorgen Peddersen
Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen@seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COMhttp://seeingmachines.com
[SEEINGMACHINES]
This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-ic...] https://twitter.com/seeingmachines [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-i...] https://www.linkedin.com/company/258949/
On Tue, 2 Oct 2018 at 03:55, Jorgen Peddersen < jorgen.peddersen@seeingmachines.com> wrote:
Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container.
There is limited experience of running the lava-server UI in docker. We don't have officially supported docker images for lava-server at this time. Work has been done with test images but those are not yet available for external users. We use lava-server in docker for the internal CI for lavasoftware.org but those images are only configured to run unit tests.
Make sure the system running docker is not already serving content on port 80 or specify a port for docker run. to use
Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djang...
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
The BRANDING support is the simplest way to see if the settings.conf is being read correctly.
https://master.lavasoftware.org/static/docs/v2/advanced-installation.html#la...
Of those, BRANDING_MESSAGE is probably the easiest to spot. https://staging.validation.linaro.org/ has a branding message - it appears in the About the LAVA staging instance section - a section which only appears if the branding message is correctly configured.
Thanks for any help you can provide regarding this matter.
Regards,
Jorgen Peddersen Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen@seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COM http://seeingmachines.com
[image: SEEINGMACHINES]
This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. https://twitter.com/seeingmachines https://www.linkedin.com/company/258949/ _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi again, From: Neil Williams neil.williams@linaro.org Sent: Tuesday, 2 October 2018 4:18 PM To: Jorgen Peddersen Cc: Lava Users Mailman list Subject: Re: [Lava-users] CSRF verification failed even after changing settings.conf
On Tue, 2 Oct 2018 at 03:55, Jorgen Peddersen <jorgen.peddersen@seeingmachines.commailto:jorgen.peddersen@seeingmachines.com> wrote:
Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container.
There is limited experience of running the lava-server UI in docker. We don't have officially supported docker images for lava-server at this time. Work has been done with test images but those are not yet available for external users. We use lava-server in docker for the internal CI for lavasoftware.orghttp://lavasoftware.org but those images are only configured to run unit tests.
Make sure the system running docker is not already serving content on port 80 or specify a port for docker run. to use
Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djang...
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
The BRANDING support is the simplest way to see if the settings.conf is being read correctly.
https://master.lavasoftware.org/static/docs/v2/advanced-installation.html#la...
Of those, BRANDING_MESSAGE is probably the easiest to spot. https://staging.validation.linaro.org/ has a branding message - it appears in the About the LAVA staging instance section - a section which only appears if the branding message is correctly configured.
Thank you for this idea. It confirms that it is not being read. I'll try to figure out why that would be now that I know it's the problem.
--
Neil Williams ============= neil.williams@linaro.orgmailto:neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Cheers, Jorgen Peddersen
Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen@seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COMhttp://seeingmachines.com
[SEEINGMACHINES]
This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-ic...] https://twitter.com/seeingmachines [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-i...] https://www.linkedin.com/company/258949/
On Tue, 2 Oct 2018 at 08:28, Jorgen Peddersen < jorgen.peddersen@seeingmachines.com> wrote:
Hi again,
*From:* Neil Williams neil.williams@linaro.org *Sent:* Tuesday, 2 October 2018 4:18 PM *To:* Jorgen Peddersen *Cc:* Lava Users Mailman list *Subject:* Re: [Lava-users] CSRF verification failed even after changing settings.conf
On Tue, 2 Oct 2018 at 03:55, Jorgen Peddersen < jorgen.peddersen@seeingmachines.com> wrote:
Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container.
There is limited experience of running the lava-server UI in docker. We don't have officially supported docker images for lava-server at this time. Work has been done with test images but those are not yet available for external users. We use lava-server in docker for the internal CI for lavasoftware.org but those images are only configured to run unit tests.
Make sure the system running docker is not already serving content on port 80 or specify a port for docker run. to use
Which docker container are you using?
I've been testing with our CI lava-server docker images and I am able to login as the user I created. (I used `docker exec -it <container> /bin/bash` to login and ran lava-server manage createsuperuser .)
Try:
docker run -p 8050:80 hub.lavasoftware.org/lava/lava/lava-server/master:2018.7-88-ga7b7939dd
Then browse to http://localhost:8050
Note: the hub.lavasoftware.org images are not yet ready for full usage, we'll write the documentation and make an announcement about those fairly soon, probably this month.
Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djang...
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
The BRANDING support is the simplest way to see if the settings.conf is being read correctly.
https://master.lavasoftware.org/static/docs/v2/advanced-installation.html#la...
Of those, BRANDING_MESSAGE is probably the easiest to spot. https://staging.validation.linaro.org/ has a branding message - it appears in the About the LAVA staging instance section - a section which only appears if the branding message is correctly configured.
Thank you for this idea. It confirms that it is not being read. I'll try to figure out why that would be now that I know it's the problem.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Cheers, Jorgen Peddersen Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen@seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COM http://seeingmachines.com
[image: SEEINGMACHINES]
This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. https://twitter.com/seeingmachines https://www.linkedin.com/company/258949/
-
Jorgen Peddersen -
Neil Williams