horizon image-elements shouldn't assume memcached cache == memcached session backend

Bug #1407752 reported by Steve McLellan on 2015-01-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Undecided
Unassigned

Bug Description

In the readme for elements/horizon:

"The Django sessions storage backend is set to LocMemCache by default. If horizon.caches.memcached is found instead not empty, the sessions storage backend is set to Memcached and the control nodes are configured as memcached locations."

This behavior was not actually the case but has been fixed so it's consistent with the docs in https://review.openstack.org/#/c/142621/

It's not obvious to me that by enabling memcached as a caching backend a user wants to handle sessions in memcached; they might want to continue using cookies (the default).

James Polley (tchaypo) on 2015-01-06
Changed in tripleo:
status: New → Confirmed
importance: Undecided → High

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, NEWTON, OCATA, PIKE, PIKE).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in tripleo:
importance: High → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers