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 fails to start when VS Code is the editor and the git repository has no devfile #21560

Closed
l0rd opened this issue Jul 19, 2022 · 4 comments
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 19, 2022

Describe the bug

If a Git repository hasn't a devfile at its root and VS Code is the editor the workspace creation fails with this error:

image

Che version

next (development version)

Steps to reproduce

On the dogfooding instance (because VS Code is the default editor there), in the Create Workspace page put the URL of a Git repo that doesn't have a Devfile in the Git repo URL (I reproduced it with https://github.com/devfile/developer-images that doesn't have a devfile yet)

On any other Che instance use a factory URL using a Git repo that doesn't have a Devfile and the parameter che-editor=che-incubator/che-code/insiders

Expected behavior

The workspace should be started using a default devfile component as mentioned in this issue and in particular here.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub, other (please specify in additional context)

Environment

Amazon

Eclipse Che Logs

No response

Additional context

No response

@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 19, 2022
@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 Jul 19, 2022
@l0rd l0rd added area/dashboard and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 19, 2022
@ibuziuk ibuziuk added the severity/P1 Has a major impact to usage or development of the system. label Jul 19, 2022
@ibuziuk ibuziuk mentioned this issue Jul 19, 2022
51 tasks
@ibuziuk ibuziuk added the status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach label Jul 27, 2022
@ibuziuk ibuziuk self-assigned this Jul 27, 2022
@ibuziuk
Copy link
Member

ibuziuk commented Aug 10, 2022

@l0rd @nickboldt @tolusha my suggestion for fixing this issue would be to set the default value for default components on the operator level e.g.

devEnvironments:
    defaultComponents:
      - container:
          image: 'quay.io/devfile/universal-developer-image:ubi8-latest'
          sourceMapping: /projects
        name: universal-developer-image

this is the config we apply to the dogfooding instance. The question is what image should we use for the Dev Spaces product taking into account that the airgap flow needs to be supported

@l0rd
Copy link
Contributor Author

l0rd commented Aug 11, 2022

@ibuziuk how is your proposal different from one in the "Expected behavior" section in this issue description? And I would rather use a fixed hash, not latest. The image should match the one used in our samples (all the samples use the same image). For Dev Spaces we currently have 3 UDI images for the samples, we should probably use the java one. cc @nickboldt

@ibuziuk
Copy link
Member

ibuziuk commented Aug 25, 2022

Fixed in eclipse-che/che-operator#1486
Closing

@ibuziuk ibuziuk closed this as completed Aug 25, 2022
@max-cx
Copy link

max-cx commented Oct 6, 2022

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3416

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

4 participants