yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #14594
[Bug 1322399] [NEW] Large-ish image uploads timeout
Public bug reported:
Uploading large-ish (> 500 MB) images into Glance through the "Create
Image" workflow times out.
To reproduce:
* Configure Horizon and Glance to live on separate machines
* Upload a large-ish image via Horizon "From File" (This is I/O-dependant, but > 500MB seems to be enough on machines with 1GB links)
Expected behavior:
An uploaded file.
Actual behavior:
It uploads the entire file, then explodes with a 500 ISE. The image
never gets uploaded.
This is because the WSGI thread receives the entire file, THEN sends it
to glance, blocking the view rendering until it's complete. If this
takes too long, modern web browsers will disconnect, causing havoc.
The "From URL" code path in Horizon (correctly, or at least not-as-
wrongly) handles this in a separate thread, and has support for a whole
bunch of AJAX-y update stuff as well. Make Horizon do that.
** Affects: horizon
Importance: Undecided
Assignee: Nicolas Simonds (nicolas.simonds)
Status: In Progress
--
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/1322399
Title:
Large-ish image uploads timeout
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
Uploading large-ish (> 500 MB) images into Glance through the "Create
Image" workflow times out.
To reproduce:
* Configure Horizon and Glance to live on separate machines
* Upload a large-ish image via Horizon "From File" (This is I/O-dependant, but > 500MB seems to be enough on machines with 1GB links)
Expected behavior:
An uploaded file.
Actual behavior:
It uploads the entire file, then explodes with a 500 ISE. The image
never gets uploaded.
This is because the WSGI thread receives the entire file, THEN sends
it to glance, blocking the view rendering until it's complete. If this
takes too long, modern web browsers will disconnect, causing havoc.
The "From URL" code path in Horizon (correctly, or at least not-as-
wrongly) handles this in a separate thread, and has support for a
whole bunch of AJAX-y update stuff as well. Make Horizon do that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1322399/+subscriptions
Follow ups
References