This has already been release. Marking as such.
** Changed in: maas (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Title:
cobbler
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Tit
** Branch linked: lp:~andreserl/maas/packaging_updates_bzr459
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Title:
cobbler_web unable to access session data due to conflict
** Changed in: cobbler (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Title:
cobbler_web unable to access session data due to conflict
What seems to be happening here is that when we set MAAS to run as
'maas' user, then the cobbler_web is also being run as 'maas' user
instead of www-data.
mod_wsgi.listener_port
'80'
HTTP_COOKIE
'sessionid=b66ddf9ffe86079a7c21c1492f978c91;
csrftoken=581c11e96343293e69aa93be4442a5a2'
mod_w
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Title:
cobbler_web unable to access session data due to conflict with maas
To manage notifications about this bug go to:
https:
