-
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
Restart from local devfile doesn't work anymore #23292
Comments
@RomanNikitenko @azatsarynnyy @vitaliy-guliy please, take a look? |
@vitaliy-guliy |
I have checked it on our dogfooding cluster (OpenShift based) and haven't found any issues. |
@batleforc does restart from local devfile work if you just add a container environment variable? |
Hi @vitaliy-guliy schemaVersion: 2.3.0
metadata:
name: WeeboDevImage
language: golang
version: 1.0.0
components:
- name: tools
container:
image: ghcr.io/batleforc/weebodevimage/che-golang:main
memoryLimit: 2Gi
mountSources: true
env:
- name: ENV
value: dev-che |
@vitaliy-guliy @RomanNikitenko @azatsarynnyy probably unrelated to this issue but today I have the following error on Developer Sandbox when trying to restart from the local devfile: for what it worth there are no self-signed certs on the rosa cluster afaik |
@ibuziuk Already had the issue in my own setup, just had to restart the full che instance to fix it |
cc: @tolusha |
@batleforc I've created a test PR che-incubator/che-code#470 |
Hi @vitaliy-guliy |
@batleforc it fails when copying the attributes, right? If yes, could you share both (of course, if it can be shared) '/projects/new-devfile.yaml' files, with and without attributes? I just want to understand whether the section contains some attributes, that we should not copy. |
@vitaliy-guliy it fails when copying the attributes 👍 and yes, there is nothing private in those manifest. Without copying the attributes:
While copying the attributes :
|
And I made absolutely no change to the devfile and encountered the problem |
Thanks, |
Describe the bug
Hi, i just made the update to the latest image and ended up being unable to use the restart from local devfile.
When I use it, the dashboard shows the screen
A full reinstall has already been done
Che version
next (development version)
Steps to reproduce
Use the restart from local devfile feature in vscode
3. Ends up with the following error
Expected behavior
To have the workspaces up and running
Runtime
Kubernetes (vanilla)
Screenshots
No response
Installation method
chectl/next
Environment
Linux
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: