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

Test UX of an upgrade to Che7 from the running Che6 workspace perspective #14810

Closed
skabashnyuk opened this issue Oct 8, 2019 · 2 comments
Closed
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

The need to verify UX of running Che6 workspace when upgrade to che 7 has happened.

  • What user will see?
  • Does this screen contain a link to the documentation that explains what to do next?
  • Does this link configurable?

Describe the solution you'd like

  • Setup che6
  • Run workspace
  • run an upgrade to che7
  • Check UX.

Describe alternatives you've considered

none

Additional context

Continuation of #14200

@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 8, 2019
@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 Oct 8, 2019
@skabashnyuk skabashnyuk added this to the 7.3.0 milestone Oct 8, 2019
@l0rd l0rd added 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 Oct 8, 2019
@mshaposhnik mshaposhnik self-assigned this Oct 10, 2019
@mshaposhnik
Copy link
Contributor

mshaposhnik commented Oct 14, 2019

To perform tests, Che6 was started using both latest and Che-6 based 1.22.GA Che operator , but che image fields in CR file was patched to use 6.19.0 version:

  • cheImageTag: '6.19.0'

Start command:
chectl server:start --installer=operator --platform=minishift --che-operator-cr-yaml=/home/Makis/projects/che/org_v1_che_cr.yaml

After that, Che6 was succesfully deployed and workspace succesfully started.

Upgrade to Che7
Upgrade was executed by changing Operator version to nightly and using patch command to update necessary images:

oc patch checluster eclipse-che --type=json -p '[{"op": "replace", "path": "/spec/server/cheImageTag", "value": "nightly"}, {"op": "replace", "path": "/spec/server/pluginRegistryImage", "value": "quay.io/eclipse/che-plugin-registry:nightly"}]' -n che

UX after update:
✔️ Workspaces was functional during update.
update_5

⚠️ Workspace were unable to open new terminal window due to lost websocket connection:
update_7

⚠️ After page reload, Che 6 workspace won't load anymore (but still running):
update_6

✔️ UD shows the warning about workspace upgrade needed:
update_1

✔️ Documentation link on how to update workspace is working OK
update_10

✔️ Newly created devfile-based Che7 workspaces are working just fine:
update_4

@mshaposhnik
Copy link
Contributor

mshaposhnik commented Oct 15, 2019

@nickboldt About the workspace updgrate docs link, it looks like the it can be overriden in
/assets/branding/product.json line 26:

"docs" : {
       "devfile" : "/docs/che-7/using-developer-environments-workspaces.html#making-a-workspace-portable-using-a-devfile_using-developer-environments-workspaces",
       "workspace" : "/docs/what-are-workspaces.html",
       "factory" : "/docs/factories-getting-started.html",
       "organization": "/docs/organizations.html",
>>     "converting": "/docs/che-7/converting-a-che-6-workspace-to-a-che-7-devfile/",
       "general": "/docs"
  }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants