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

Workspace created by compose recipe url does not start (regression) #3765

Closed
artaleks9 opened this issue Jan 17, 2017 · 5 comments
Closed

Workspace created by compose recipe url does not start (regression) #3765

artaleks9 opened this issue Jan 17, 2017 · 5 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@artaleks9
Copy link
Contributor

When I try to create workspace by compose recipe url from stack import, then workspace does not start.

Reproduction Steps:

Expected behavior:
workspace should be created.

Observed behavior:
workspace is not created and there is unexpected error.

Che version: 5.1.0-SNAPSHOT
OS and version: Ubuntu 14.04
Docker version: 1.12

Che cli.log output: cli.log.zip

Additional information:

  • Problem can be reliably reproduced, doesn't happen randomly: [Yes]
  • See the attachment:

imp_compfile_che
imp_compfile_nightly

@artaleks9 artaleks9 added the kind/bug Outline of a bug - must adhere to the bug report template. label Jan 17, 2017
@riuvshin riuvshin changed the title Workspace created by compose recipe url does not start Workspace created by compose recipe url does not start (regression) Jan 17, 2017
@riuvshin
Copy link
Contributor

@TylerJewell @garagatyi guys seems this is regression it was working last week. should we mark this as blocker for 5.1.0 ?

@artaleks9
Copy link
Contributor Author

Yesterday it worked.

@riuvshin riuvshin added this to the 5.1.0 milestone Jan 17, 2017
@JamesDrummond JamesDrummond added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Jan 17, 2017
@benoitf
Copy link
Contributor

benoitf commented Jan 17, 2017

@artaleks9 do you have server traces ?

@garagatyi
Copy link

It is because of NPE on server side

@riuvshin
Copy link
Contributor

nice, ty @evoevodin !

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. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

5 participants