Last modified: 2014-09-23 22:58:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47483, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 45483 - Make instance creation failures more verbose
Make instance creation failures more verbose
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-02-27 11:27 UTC by Silke Meyer (WMDE)
Modified: 2014-09-23 22:58 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

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

Description Silke Meyer (WMDE) 2013-02-27 11:27:13 UTC 
When the creation of new Labs instances fails, it would be good to get some more output if possible. Now I just see "Failed to create instance".
Comment 1 Ryan Lane 2013-02-27 19:26:10 UTC 
Yes, we should pass-through error messages from the API.

If you are having failures, please find me on irc. It's likely a quota issue.
Comment 2 Sumana Harihareswara 2013-03-26 19:56:19 UTC 
I spoke with Andrew Bogott about this issue this week, and he said that this is technically a user interface problem, but "getting detailed error messages from openstack is pretty complicated since the failures are [asynchronous]... So not so much a design problem as a 'not worth the months it would take to do right' problem :)"

I'm leaving this note here for anyone in the future who wants to work on solving this problem.
Comment 3 Ryan Lane 2013-03-27 03:18:50 UTC 
Some of the failures are asynchronous, but a lot of the error messages are returned immediately on the API call; we're just not passing them through to the end-user. Additionally, any of the errors that are asynchronous can also be pulled with appropriate API calls, we're just not exposing that. Passing through the immediate failures is likely a pretty easy fix.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links