Skip to content

Latest commit

 

History

History
89 lines (57 loc) · 3.69 KB

HELP.md

File metadata and controls

89 lines (57 loc) · 3.69 KB
Raw

🆘 CodeReady Workspaces for Enablement 🆘 HELP FOR THE NEEDY 🆘

Temporary help guide whilst we settle in CRW to enablement.

Product Documentation

Common Errors

Provide some guidance for current common issues encountered with CRW and Enablement

Error Starting Workspace

Users browse to the factory URL and see the not a valid zip error on starting workspace

not-a-valid-zip

FIX - Not fatal, the users workspace has been created.

  • fix is to just get the user to manually start there created workspace
  • browse to dashboard as the user https://codeready-workspaces.apps.<DOMAIN_FOR_YOUR_CLASS>/dashboard
  • Start the workspace Actions > triangle start

not-a-valid-zip-fix

I Have Lost the Magic Factory Link!

Users are asking you for the magic link to create the cloud IDE and the SRE is on a coffee break. From Excercise.1

https://codeready-workspaces.apps.<DOMAIN_FOR_YOUR_CLASS>/dashboard/#/load-factory?name=DO500%20Template&user=admin

NOTE - Complete URL should be replaced with the one you've been provided by the instructor.

FIX - Not fatal, use the force. The `factory` is only available to the `admin` user in CRW - hence the `&user=admin` bit on the end of the link (dont change this !).

  • Login to dashboard URL (https://codeready-workspaces.apps.<DOMAIN_FOR_YOUR_CLASS>/dashboard) using the admin user (in keycloak/SSO) which is deployed to the CRW namespace
  • Browse to Factories > DO500 Template

admin-login-crw factory-link

Longer term we should fix up the admin user creds as well ! - #17

Multiple workspaces created by users

Not strictly a bug, more a feature, but due to the error starting a workspace, the frantic user has started smashing the Reload button in their browser. Each invocation of the factory link, creates a new workspace - which could make for some fun resource hogging.

FIX - Not fatal unless your cluster runs out of resources 🤠

  • Ask the users to stop or delete not/in-use workspaces
  • browse to dashboard as the user https://codeready-workspaces.apps.<DOMAIN_FOR_YOUR_CLASS>/dashboard
  • Stop the workspaces not in use Actions > square stop

Longer term we should limit these - #18

Stuck namespaces that are always 'Terminating' ?

Seems that the Che CR holds onto storage resources (i think).. if you want to delete a projects that is being stubourn

Good Luck 🤠🤠🤠

APIURL=https://master.cluster.example.com:443
for i in $( oc get ns | grep Terminating | awk '{print $1}'); do echo $i; oc get ns $i -o json| jq "del(.spec.finalizers[0])"> "$i.json"; curl -k -H "Authorization: Bearer $(oc whoami -t)" -H "Content-Type: application/json" -X PUT --data-binary @"$i.json" "$APIURL/api/v1/namespaces/$i/finalize"; done
for i in $(oc get pvc | grep Terminating| awk '{print $1}'); do oc patch pvc $i --type='json' -p='[{"op": "replace", "path": "/metadata/finalizers", "value":[]}]'; done
for i in $(oc get pv | grep Released| awk '{print $1}'); do oc patch pv $i --type='json' -p='[{"op": "replace", "path": "/metadata/finalizers", "value":[]}]'; done

Who do i call in an emergency?

  • 📴 a.team 📴 b.mak 📴