mirror of
https://github.com/retspen/webvirtmgr.git
synced 2026-04-25 07:35:50 +03:00
[GH-ISSUE #592] Django 1.7+ compatibility #445
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wildstray on GitHub (Jan 12, 2016).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/592
I upgraded OS to Debian 8.2 "Jessie" so python-django was updated to 1.7.7. Since that moment I'm experiencing many major issues.
In /etc/supervisor/conf.d/webvirtmgr.conf I had to change command to:
In /opt/webvirtmgr/console/webvirtmgr-console I had to add after os.environ.setdefault("DJANGO_SETTINGS_MODULE", "webvirtmgr.settings"):
Now webvirtmgr is "semi-usable" "semi-working"... console random fails for some guests (and not with some others, I've no explanations), this is the traceback:
Likewise, graphs (hostdetails, instdetails) are not working anymore due to cookies (functions get_cookie, set_cookie and direct access to cookies) as it seems that object WSGIRequest doesn't expose them anymore.
I'm using last webvirtmgr version from git...
@wildstray commented on GitHub (Jan 13, 2016):
Just solved the console issue deleting all records of instance_instance table of /opt/webvirtmgr/webvirtmgr.sqlite3
Now all server console connects (but it isn't stable as it was with django 1.5.5+, I'm experiencing disconnections...).
Unluckily this does not solve issues with 'WSGIRequest' object has no attribute '_get_cookies'...
@wildstray commented on GitHub (Jan 13, 2016):
...using request.session instead of request._get_cookies and response.cookie might be a solution?
@wildstray commented on GitHub (Jan 13, 2016):
A little patch (far from beeing perfect... eg. CPU usage for guest seems to be always 0 also if there is load...)
@wildstray commented on GitHub (Jan 15, 2016):
@purplesrl commented on GitHub (Jun 13, 2016):
https://github.com/retspen/webvirtmgr/issues/613
@rapgro commented on GitHub (Nov 26, 2017):
"Per our supported versions policy, Django 1.5 and 1.6 are no longer receiving security updates." since at least CVE-2015-5145. See also CVE-2015-5144.