As an Admin, I want to have clear instructions for switching to Dev Workspace engine

[ibuziuk]

Is your task related to a problem? Please describe

As an Admin, I want to have clear instructions for swithing from Che Server to Dev Workspace Engine.

Describe the solution you'd like

As an Admin, I want to have clear instructions for swithing from Che Server to Dev Workspace Engine (stable or next channels).

Describe alternatives you've considered

No response

Additional context

No response

[themr0c]

Referenced in https://issues.redhat.com/browse/RHDEVDOCS-3372

[ibuziuk]

SOP that I tried so far, and which does not work as expected (details below):

• install 'eclipse-che' using the stable channel
• create CR with a single-host and OpenShift Auth enabled
• create an account (using 'developer' OpenShift account on the crc for example) with a couple of workspaces and start one of them
• wait until workspace is running, run build / run command
• start preparations for the migration procedure from the stable to tech-preview-stable-all-namespace
• delete eclipse-che subscription from the namespace

[ibuziuk@fedora ~]$ oc get subscription
NAME          PACKAGE       SOURCE                CHANNEL
eclipse-che   eclipse-che   community-operators   stable
[ibuziuk@fedora ~]$ oc delete subscription eclipse-che
subscription.operators.coreos.com "eclipse-che" deleted

• delete csv and dependent objects
  
• IMPORTANT! Do not delete previously created CR / CRD
• operator pod in the namespace will be terminated
  
• install 'eclipse-che' using the tech-preview-stable-all-namespace
  
• operators are installed in the all-namespace mode as expected
  
• update the CR from the eclipse-che namespace and enable devWorkspace

  devWorkspace:
    enable: true

• go back to the running workspace
• session expired / re-login is required
• login using the existing 'developer' account that was used previously
• ERROR: on the 'eclipse-che' end the new account is created

• ERROR: UD shows the following errors
  

• Start a new DevWorkspace

• ERROR: Workspace is started, but since the account is different, in a different namespace (not developer-dev, but
  developeryv6z-dev)
  

• ERROR: previously running workspace pod (the one that has been started before migration in the developer-che namespace) is still running.

Basically, there are two main issues with the switch from the stable to tech-preview-stable-all-namespace channel

1. for some reason, a new account is created after the devWorkspace switch, which is utterly unexpected New account is created after switching an existing Eclipse Che instance from 'stable' -> 'tech-preview-stable-all-namespace' channel, and enabling DevWorkspace engine #20629

dbche=# SELECT * from account;
                  id                  |     name      |   type   
--------------------------------------+---------------+----------
 434d4bdf-7bae-47de-b657-9c3d675bf4d2 | developer     | personal
 e8a1a712-743c-4978-b095-9b3db488a110 | developeryv6z | personal
(2 rows)

2. previously running workspaces managed by che-server are not stopped (when admin switches the engine to DevWorskpace all che-server based workspaces should be stopped) When admin switches the engine to DevWorskpace all che-server based workspaces should be stopped #20631

[benoitf]

moving issue to 7.42 milestone as this issue is part of the endgame

[ibuziuk]

Fixed as part of eclipse-che/che-docs#2269