Some actions require a manual page reload to see changed data

[Kieran Spear]

When you detach a volume from an instance, the page is redirected to the volumes index page. Because the volume detach process is asynchronous, it's possible that this page load happens before the status of the volume has been changed, so the page load sees the volume as still attached. This requires a manual refresh to see the actual state of the volume (and for the correct action buttons to show up in the table).

This can probably occur in other cases where there's a race condition between the next page load and the object actually being updated in the relevant service API DB.

We might need some concept of "expected status" so that we can trigger ajax calls on rows that aren't necessarily in a transition state like "Creating" or "Deleting", but still require updates.

[Gary W. Smith (gary-w-smith)]

Moving to low since there is a fairly obvious workaround for it (browser reload button). This behavior can be seen in horizon for other asynchronous operations as well.

[Jeffrey Olsen (jeffrey-olsen)]

Maybe adding a reload icon in Horizon that refreshes instead of using the browser refresh. Yes, some of us are lazy :)

[Timur Sufiev (tsufiev-x)]

There is a concept of UNKNOWN status for an entity in Horizon datatables, which causes AJAX calls to be issued regularly until the status changes either to UP or DOWN. Is it possible to add another status for volume, namely 'Detaching' which fits in UNKNOWN statuses group? Seems like the most natural solution.

[Marcos Lobo (marcos-fermin-lobo)]

I confirm this issue in Icehouse.