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

Workspaces failed to start with SSH key configured #22625

Closed
akurinnoy opened this issue Oct 23, 2023 · 2 comments
Closed

Workspaces failed to start with SSH key configured #22625

akurinnoy opened this issue Oct 23, 2023 · 2 comments
Labels
area/devworkspace-operator kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@akurinnoy
Copy link
Contributor

akurinnoy commented Oct 23, 2023

Describe the bug

On the dogfooding cluster, I configured the SSH keys to use in my workspaces as described here. With the secret configured, my workspaces were constantly failing to start with the error: Error creating DevWorkspace deployment: Init Container che-code-injector has state CreateContainerError.

Removing the secret eliminates the problem.

Steps to reproduce

  1. Configure DevWorkspaces to use SSH keys for Git operations
  2. Start any workspace

Expected behavior

Workspace is running.

Screenshots

Progress

Screenshot 2023-10-23 at 17 10 33

Events

Screenshot 2023-10-23 at 17 33 10

@akurinnoy akurinnoy added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 23, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 23, 2023
@amisevsk
Copy link
Contributor

I tested this briefly with Che next and wasn't able to reproduce the issue -- I suspect it may be occurring due to a file mounting collision (e.g. two secrets that mount the same file name to the same path, ssh_config for example) and have opened devfile/devworkspace-operator#1194 preemptively (since it seems like DWO is not currently checking for such collisions)

@akurinnoy
Copy link
Contributor Author

@amisevsk thank you for the hint! I went through the list of secrets and found another SSH key secret created a long time ago. Removing the extra one secret resolved the issue.

@akurinnoy akurinnoy removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devworkspace-operator kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

3 participants