Fuel UI spins with running progress bar

Bug #1656958 reported by Roman Rufanov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
Undecided
Unassigned
8.0.x
Confirmed
High
Unassigned
Mitaka
Confirmed
High
Unassigned
Newton
New
Undecided
Unassigned

Bug Description

Env: Fuel 9.1 in VirtualBox 5.1.12 on Windows 7 Pro with 8 GB of memory with Chrome browser
Also confirmed on 32GB Linux with Chrome browser.

Scenario A (pics 1 to 3):
1) Install OpenStack and open Fuel to some page (say http://10.20.0.2:8000/#cluster/1/dashboard)
2) Suspend all VirtualBox nodes (I am using VirtualBox for Windows)
3) Resume VirtualBox nodes
4) Refresh page in Fuel UI or click anywhere in Fuel

Expected: page will open
Actual: progress bar grows and never ends
Workaround: I had to clear browsing history for 1 days and then re-login into Fuel and everything started working

Scenario B (pics 4 and 5):
1) Install OpenStack and have it running
2) Open Fuel page (say http://10.20.0.2:8000/#cluster/1/dashboard) in Chrome
2) Close Chrome
3) Open Chrome and try to go same page http://10.20.0.2:8000/#cluster/1/dashboard

Expected: page will open
Actual: empty page (pic 4 and 5)
Workaround: clear browsing history for 1 day and then re-login into Fuel and everything started working OR open Incognito windows and re-login into Fuel

It seems it is affected by Two errors:
1. api/version always gives 401, even on login screen (while "fuel fuel-version" works fine in CLI)
2.After clicking on the banner of an existing cluster (and generally on any other UI element which should navigate to a different page):

Revision history for this message
Roman Rufanov (rrufanov) wrote :
Revision history for this message
Roman Rufanov (rrufanov) wrote :

See files with detail error screenshots

Revision history for this message
Roman Rufanov (rrufanov) wrote :

possible causes: by storing keystone token in 2 places: cookies and localStorage.
possible fix: switching to Keystone V3 API: https://review.openstack.org/#/c/379387/.
If this patch actually fixes the issue, I see 2 ways how we could proceed:
Cherry-pick both fuel-ui and nailgun patches to stable/mitaka.
Re-implement fuel-ui patch to fix 2 sources of truth issue but keep using Keystone V2 API so cherry-pick of the patch to nailgun won't be necessary.

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Duplicate of 1656822, already in progress.

Changed in fuel:
milestone: none → 11.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.