Bug 496759 - Two-stage refresh temporarily leaves app without URL and may cause errors
Summary: Two-stage refresh temporarily leaves app without URL and may cause errors
Status: NEW
Alias: None
Product: CFT
Classification: ECD
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal
Target Milestone: 1.1.0 M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2016-06-24 16:33 EDT by Nieraj Singh CLA
Modified: 2017-05-19 14:28 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nieraj Singh CLA 2016-06-24 16:33:36 EDT 
The two-stage refresh introduced in CFT 1.0 quickly fetches basic stats of an application in the first stage, and details in the second.

However, fetching URL occurs in the second stage, which means that while waiting for the second stage to complete, applications may not have URLs set in the Cloud module, which can result in errors if a user attempts to perform operations on the app while refresh is happening (e.g. unable to navigate to app, URL errors during restart/publish app).

If the user allows refresh to complete, this is not a problem.
Comment 1 Nieraj Singh CLA 2017-03-09 14:56:01 EST 
We should fix this for Oxygen. If we are doing two-stage refresh, leaving an incomplete module that a user can interact with will cause problems.

One option is that during the first stage of the refresh, we only remove modules that no longer exist, but do not update the actual module CF information, leaving the old information while the second stage completes.

Another, and more complex option, is to block users from performing operations while a refresh is in progress, and show an info or warning to wait while refresh completes.