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

Failed to request factory resolver namespaces not found #20420

Closed
mtsmfm opened this issue Sep 6, 2021 · 2 comments
Closed

Failed to request factory resolver namespaces not found #20420

mtsmfm opened this issue Sep 6, 2021 · 2 comments
Labels
area/che-server area/factory/server Server side of factory implementation 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.

Comments

@mtsmfm
Copy link
Contributor

mtsmfm commented Sep 6, 2021

Describe the bug

It seems we can't create new workspace with Import from Git if the repo doesn't have devfile.yaml and it's first time to create workspace.

Che version

7.35@latest

Steps to reproduce

  1. Setup eclipse che
  2. Create workspace with Import from Git and input https://github.com/eclipse/che
    image

Expected behavior

A workspace is created successfully

Runtime

Kubernetes (vanilla), Docker Desktop

Screenshots

image

Installation method

chectl/latest

Environment

Windows, Amazon

Eclipse Che Logs

https://che-eclipse-che.che.127.0.0.1.nip.io/api/factory/resolver/ returns 400 and the response message is

Error occurred during creation a workspace from devfile located at `https://raw.githubusercontent.com/eclipse/che/HEAD/devfile.yaml`. Cause: Failure executing: POST at: https://10.96.0.1/api/v1/namespaces/mtsmfm-che/secrets. Message: namespaces "mtsmfm-che" not found. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=namespaces, name=mtsmfm-che, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=namespaces "mtsmfm-che" not found, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=NotFound, status=Failure, additionalProperties={}).

Additional context

I can't find any log on che server component with the following steps:

  1. Run the following command
$ kubectl logs -n eclipse-che -l component=che --follow
  1. Do the Steps to reproduce

I think you can easily reproduce this problem with kubectl delete ns <yourname>-che

@mtsmfm mtsmfm added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 6, 2021
@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 Sep 6, 2021
@skabashnyuk
Copy link
Contributor

Duplicates #19236 and should be fixed #20167
Workaround - create at least one workspace.

@skabashnyuk skabashnyuk added area/che-server area/factory/server Server side of factory implementation severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 6, 2021
@mtsmfm
Copy link
Contributor Author

mtsmfm commented Sep 6, 2021

@skabashnyuk Thank you for pointing out.
I searched issues with some keywords like "namespace not found" though I overlooked them.

@mtsmfm mtsmfm closed this as completed Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server area/factory/server Server side of factory implementation 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.
Projects
None yet
Development

No branches or pull requests

3 participants