yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #87727
[Bug 1952112] [NEW] Template topology page doesn't handle session expiration
Public bug reported:
Reproduced on master, but any release since about Pike seems to be
affected.
Steps to reproduce:
1. Deploy any Openstack environment with Heat and heat-dashboard components enabled. Devstack should be enough
2. Create any stack. "Most basic template" from https://docs.openstack.org/heat/victoria/template_guide/hot_guide.html should work well after passing valid image name
3. Go to Project->Orchestration->Stacks->created stack->Topology tab
4. Wait until session timeout (1 hour by default) or mangle sessionid cookie value in browser to make it invalid
Actual behavior:
Visually nothing changed, but repeating requests to <hostname>/project/stacks/get_d3_data/<stack_id> return 401. Server-side logs are also affected.
Expected behavior:
Some form of logout or notification about expired user session
** 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/1952112
Title:
Template topology page doesn't handle session expiration
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Reproduced on master, but any release since about Pike seems to be
affected.
Steps to reproduce:
1. Deploy any Openstack environment with Heat and heat-dashboard components enabled. Devstack should be enough
2. Create any stack. "Most basic template" from https://docs.openstack.org/heat/victoria/template_guide/hot_guide.html should work well after passing valid image name
3. Go to Project->Orchestration->Stacks->created stack->Topology tab
4. Wait until session timeout (1 hour by default) or mangle sessionid cookie value in browser to make it invalid
Actual behavior:
Visually nothing changed, but repeating requests to <hostname>/project/stacks/get_d3_data/<stack_id> return 401. Server-side logs are also affected.
Expected behavior:
Some form of logout or notification about expired user session
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1952112/+subscriptions
Follow ups