Public bug reported:
If horizon is being run with memcached, the memcached service must be
restarted after horizon is upgraded from one openstack release to
another.
If memcached isn't restarted, I'm noticing the horizon theme and
possibly static assets are not being applied correctly.
Restarting memcached isn't a huge issue if memcached is running locally
but if run distributed where memcached is on a different node from
horizon then it gets harder to manage.
Ideally horizon would just work after upgrade without a memcached
restart.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1660695
Title:
memcached restart required after horizon upgrade
Status in OpenStack Dashboard (Horizon):
New
Bug description:
If horizon is being run with memcached, the memcached service must be
restarted after horizon is upgraded from one openstack release to
another.
If memcached isn't restarted, I'm noticing the horizon theme and
possibly static assets are not being applied correctly.
Restarting memcached isn't a huge issue if memcached is running
locally but if run distributed where memcached is on a different node
from horizon then it gets harder to manage.
Ideally horizon would just work after upgrade without a memcached
restart.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1660695/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
