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

After upgrading from 7.41.x converted workspaces fail to start #21329

Closed
Tracked by #21318
l0rd opened this issue Apr 11, 2022 · 3 comments
Closed
Tracked by #21318

After upgrading from 7.41.x converted workspaces fail to start #21329

l0rd opened this issue Apr 11, 2022 · 3 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.

Comments

@l0rd
Copy link
Contributor

l0rd commented Apr 11, 2022

Describe the bug

I have followed instructions to upgrade a Che v7.41 instance. My user had a couple of existing workspaces (chectl and devworkspaces-operator) that, after the upgrade, required to be converted in order to be used. After clicking on the convert button and then open the workspaces are not started:

The workspaces are stucked as "starting" in the dashboard:

image

But the correspondent DevWorkspace phase is Stopped:

image

And if I go back to "My Workspaces" it appears twice:
image

And when selecting it: it's a v2.1 but deprecated (but doesn’t allow to convert or start it anymore):
image

Che version

7.44@latest

Steps to reproduce

  1. Deploy Che v7.41 using chectl on OpenShift
  2. Use a factory link to start a chectl workspace: https://<che-host>/#https://github.com/che-incubator/chectl
  3. Follow the upgrade guide
  4. Try to convert and start the workspace

Expected behavior

Converted workspaces start successufully

Runtime

OpenShift

Installation method

chectl/latest

Environment

macOS

@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 11, 2022
@l0rd l0rd mentioned this issue Apr 11, 2022
45 tasks
@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 Apr 11, 2022
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. 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 Apr 11, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Apr 11, 2022

@ibuziuk I have added this issue to the sprint plan

@ibuziuk
Copy link
Member

ibuziuk commented Apr 12, 2022

@l0rd this issue should have been fixed in 7.46.0 as part of #21208

@ibuziuk ibuziuk self-assigned this Apr 12, 2022
@ibuziuk
Copy link
Member

ibuziuk commented Apr 14, 2022

Closing, feel free to reopen if still reproducible against 7.46

@ibuziuk ibuziuk closed this as completed Apr 14, 2022
@ibuziuk ibuziuk mentioned this issue Apr 25, 2022
58 tasks
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.
Projects
None yet
Development

No branches or pull requests

3 participants