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

After applying new exec agent some commands may be invalid #3438

Closed
musienko-maxim opened this issue Dec 19, 2016 · 2 comments
Closed

After applying new exec agent some commands may be invalid #3438

musienko-maxim opened this issue Dec 19, 2016 · 2 comments
Assignees
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

@musienko-maxim
Copy link
Contributor

musienko-maxim commented Dec 19, 2016

Reproduction Steps:

  1. We used only shell commands before the exec agent. But exec agent bash command. In this way many commands that was written early may not work.
    It may create many unexpected errors for users of the Codenvy.
    For example: echo -e '123' > ~/test.txt
    Expected behavior:
    should be created file with content like: 123
    Observed behavior:
    we have file with content like: -e 123

Che version: 5.0.0-M9
OS and version: Ubuntu 14.0 TLS
Docker version: 1.12.1
Che install: Docker container

@musienko-maxim musienko-maxim added 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. labels Dec 19, 2016
@TylerJewell TylerJewell added this to the 5.0.0-M9 milestone Dec 19, 2016
@garagatyi
Copy link

Can you specify stack or WS config that was the source of workspace?

@musienko-maxim
Copy link
Contributor Author

musienko-maxim commented Dec 20, 2016

Go to the nigtly5 or nigtly server and create workspace from java stack for example.

@vkuznyetsov vkuznyetsov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/enterprise sprint/next labels Dec 20, 2016
@tolusha tolusha self-assigned this Dec 21, 2016
@tolusha tolusha added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Dec 21, 2016
@tolusha tolusha added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Dec 22, 2016
@tolusha tolusha removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Dec 26, 2016
@tolusha tolusha closed this as completed Dec 26, 2016
@bmicklea bmicklea mentioned this issue Jan 13, 2017
70 tasks
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