Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newly created workspace is stopped and gives 503 #497

Closed
siliconalchemy opened this issue Feb 24, 2016 · 3 comments
Closed

Newly created workspace is stopped and gives 503 #497

siliconalchemy opened this issue Feb 24, 2016 · 3 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@siliconalchemy
Copy link

Created new workspace from ready-to-go node stack. Workspace is created immediately:
2016-02-24 17:07:12,058[nio-8080-exec-9] [INFO ] [o.e.c.a.w.s.WorkspaceManager 140] - EVENT#workspace-created# WS#default# WS-ID#workspacef4refa2ij5yqofhw# USER#che#

Browser gives this error in the console:
http://xxx.net:8080/api/ext/project/workspacef4refa2ij5yqofhw 503 (Service Unavailable)
This shows in a browser as:
HTTP Status 503 - Request can't be forwarded to machine. Dev machine of workspace workspacef4refa2ij5yqofhw is not running.

I would expect the workspace to start as part of the creation process, and/or the api call should be handled by the server or client gracefully rather than giving 503 error.

@ghost ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label Feb 25, 2016
@ghost
Copy link

ghost commented Feb 25, 2016

Actually, when you create a workspace, you do not automatically run it. You may create it but not run in fact.

As to this API call, I'll check with User Dashboard team.

@ddementieva ddementieva added kind/bug Outline of a bug - must adhere to the bug report template. and removed kind/question Questions that haven't been identified as being feature requests or bugs. labels Feb 26, 2016
@ghost
Copy link

ghost commented Feb 26, 2016

Issue confirmed. Will be fixed in the upcoming sprint.

@ghost
Copy link

ghost commented Apr 23, 2016

Fixed

@ghost ghost closed this as completed Apr 23, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants