Good morning everyone,
I would like to know if someone here already face the following message while opening a LAVA results page or LAVA alljobs page :
I am looking around LAVA documentation to check if it is a known issue. But if someone here already knows something about it, it could help me also.
regards,
Hi Conrad,
I had exactly the same issue with LAVA 2018.02. It is related with python-django version. Refer to https://docs.djangoproject.com/en/1.11/releases/1.11/#django-template-backen... . V1.11 will be installed when using 'apt install -y -t stretch-backports lava-server' to install lava-sever from backports. I filed a ticket for this issue https://projects.linaro.org/browse/CTT-990
Before it is fixed, you may try the following to downgrade the package to v1.10 that from main repo.
# dpkg -r --force-all python-django # dpkg -r --force-all python3-django # dpkg -r --force-all python-django-common # apt --fix-broken install
-- Thanks, Chase
On 14 March 2018 at 01:36, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I would like to know if someone here already face the following message while opening a LAVA results page or LAVA alljobs page :
I am looking around LAVA documentation to check if it is a known issue. But if someone here already knows something about it, it could help me also.
regards,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hello,
The problem seems to come from django-tables2 version in debian stretch.
As a *work around*, installing python-django-tables2 from unstable does fix the issue.
wget http://deb.debian.org/debian/pool/main/d/django-tables/python-django-tables2... dpkg -i python-django-tables2_1.14.2-1_all.deb
We will investigate for a proper fix.
Cheers.
2018-03-14 0:34 GMT+01:00 Chase Qi chase.qi@linaro.org:
Hi Conrad,
I had exactly the same issue with LAVA 2018.02. It is related with python-django version. Refer to https://docs.djangoproject. com/en/1.11/releases/1.11/#django-template-backends- django-template-render-prohibits-non-dict-context . V1.11 will be installed when using 'apt install -y -t stretch-backports lava-server' to install lava-sever from backports. I filed a ticket for this issue https://projects.linaro.org/browse/CTT-990
Before it is fixed, you may try the following to downgrade the package to v1.10 that from main repo.
# dpkg -r --force-all python-django # dpkg -r --force-all python3-django # dpkg -r --force-all python-django-common # apt --fix-broken install
-- Thanks, Chase
On 14 March 2018 at 01:36, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I would like to know if someone here already face the following message while opening a LAVA results page or LAVA alljobs page :
I am looking around LAVA documentation to check if it is a known issue. But if someone here already knows something about it, it could help me also.
regards,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Good morning Chase, Remi,
Thank you for your answers.
Chase, I checked the ticket you filled for that issue. It is well explained. However, I tried Remi's work around method first as it seemed to be a faster way and it worked fine. I am going to keep your ticket in mind for later debugging.
regards,
On 14 March 2018 at 08:58, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
The problem seems to come from django-tables2 version in debian stretch.
As a *work around*, installing python-django-tables2 from unstable does fix the issue.
wget http://deb.debian.org/debian/pool/main/d/django-tables/ python-django-tables2_1.14.2-1_all.ded dpkg -i python-django-tables2_1.14.2-1_all.deb
We will investigate for a proper fix.
Cheers.
2018-03-14 0:34 GMT+01:00 Chase Qi chase.qi@linaro.org:
Hi Conrad,
I had exactly the same issue with LAVA 2018.02. It is related with python-django version. Refer to https://docs.djangoproject.com /en/1.11/releases/1.11/#django-template-backends-django- template-render-prohibits-non-dict-context . V1.11 will be installed when using 'apt install -y -t stretch-backports lava-server' to install lava-sever from backports. I filed a ticket for this issue https://projects.linaro.org/browse/CTT-990
Before it is fixed, you may try the following to downgrade the package to v1.10 that from main repo.
# dpkg -r --force-all python-django # dpkg -r --force-all python3-django # dpkg -r --force-all python-django-common # apt --fix-broken install
-- Thanks, Chase
On 14 March 2018 at 01:36, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I would like to know if someone here already face the following message while opening a LAVA results page or LAVA alljobs page :
I am looking around LAVA documentation to check if it is a known issue. But if someone here already knows something about it, it could help me also.
regards,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team
On 14 March 2018 at 10:26, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning Chase, Remi,
Thank you for your answers.
Chase, I checked the ticket you filled for that issue. It is well explained.
Ticket: https://projects.linaro.org/browse/CTT-990
If you don't have access to that ticket, the cloned LAVA story contains the implementation: https://projects.linaro.org/browse/LAVA-1258
The fix is now available: https://tracker.debian.org/news/941861/accepted-django-tables-1142-1bpo91-so...
Essentially, when a new version of python-django is uploaded to stretch-backports, there can be a need to update the version of django-tables2 in stretch-backports as well. This process is not automatic.
However, I tried Remi's work around method first as it seemed to be a faster way and it worked fine. I am going to keep your ticket in mind for later debugging.
regards,
On 14 March 2018 at 08:58, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
The problem seems to come from django-tables2 version in debian stretch.
As a *work around*, installing python-django-tables2 from unstable does fix the issue.
wget http://deb.debian.org/debian/pool/main/d/django-tables/pytho n-django-tables2_1.14.2-1_all.ded dpkg -i python-django-tables2_1.14.2-1_all.deb
We will investigate for a proper fix.
Cheers.
2018-03-14 0:34 GMT+01:00 Chase Qi chase.qi@linaro.org:
Hi Conrad,
I had exactly the same issue with LAVA 2018.02. It is related with python-django version. Refer to https://docs.djangoproject.com /en/1.11/releases/1.11/#django-template-backends-django-temp late-render-prohibits-non-dict-context . V1.11 will be installed when using 'apt install -y -t stretch-backports lava-server' to install lava-sever from backports. I filed a ticket for this issue https://projects.linaro.org/browse/CTT-990
Before it is fixed, you may try the following to downgrade the package to v1.10 that from main repo.
# dpkg -r --force-all python-django # dpkg -r --force-all python3-django # dpkg -r --force-all python-django-common # apt --fix-broken install
-- Thanks, Chase
On 14 March 2018 at 01:36, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I would like to know if someone here already face the following message while opening a LAVA results page or LAVA alljobs page :
I am looking around LAVA documentation to check if it is a known issue. But if someone here already knows something about it, it could help me also.
regards,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
-
Chase Qi -
Conrad Djedjebi -
Neil Williams -
Remi Duraffort