-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Regression] Automatically restart from local devfile when devfile failed to be resolved at startup #23277
Comments
@dmytro-ndp we do need a test case for this scenario:
N.B. no OAuth / PAT are configured |
@ibuziuk : could you please confirm, that there should be no any additional warnings during workspace startup via private SSH URL, such as the following, when SSH key is configured?: |
@vinokurig @dmytro-ndp can we close for 7.95.0 ? |
+1 to close it for 7.95.0 We will reopen the issue if reproduce it in DS 3.18.0. |
Closing in favor of #23364 |
Describe the bug
This functionality is currently broken - #22491
There are situation where che-server is not able to resolve a devfile from a git repository using the git service API. A typical example is when it's not GitHub, GitLab, Bitbucket or Azure DevOps repository or when SSH URL is used.
Che version
7.95@latest
Steps to reproduce
Currently dashboard just proposes user to continue with the default devfile, which is not expected.
Expected behavior
controller.devfile.io/bootstrap-devworkspace: true
when Devfile resolution via API fails or is not supported by che-server - Add attributecontroller.devfile.io/bootstrap-devworkspace: true
when Devfile resolution via API fails or is not supported #22697Runtime
OpenShift
Screenshots
No response
Installation method
OperatorHub
Environment
Linux
Eclipse Che Logs
No response
Additional context
related DWO PR - devfile/devworkspace-operator#1193
The text was updated successfully, but these errors were encountered: