[chectl] workspace:inject no more finding default workspace pod

[apupier]

Describe the bug

[apupier@linux ~]$ chectl workspace:inject -k
  ✔ Verify if namespace che exists
  ✖ Verify if the workspaces is running
    → No workspace pod is found
    Injecting configurations
 ›   Error: No workspace pod is found

Che version

• latest 7.9.0-SNASPHOT
• nightly
• other: please specify

Steps to reproduce

1. Start a workspace and wait that it has been started
2. call chectl workspace:inject -k from host
3. See error

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Additional context

[tolusha]

@apupier
In which namespace the workspace is run?
If it isn't che then could you try with -n <namespace> flag?

[apupier]

In which namespace the workspace is run?

it should be in che namespace as I installed with chectl server:start -p minikube

[tolusha]

yeap, but could you double check pls?

[apupier]

I have 2 namespaces available:
che and che-che

in deployments, there is a "workspacexxxx" for che-che, looks alike the che is containing "only" devfile-registry-xxx, plugin-registry-xxx and a che-xxxx

[apupier]

[apupier@linux ~]$ chectl workspace:inject -k -n che-che
  ✔ Verify if namespace che-che exists
  ✔ Verify if the workspaces is running
  ✔ Injecting configurations

looks alike now the namespace by defautl to look at has changed and is che-che instead of che

[tolusha]

yes, workspace goes in a different namspace.
Can we close the issue?

[apupier]

I think we need to keep it open and adjust the behavior of chectl workspace:inject to match the new default behavior.

It sounds like a regression

[tolusha]

In general way chectl doesn't know where workspace is created

[tolusha]

But I do agree the chectl might be smarter

[apupier]

why the severity is only P2 although it is a regression?

[tolusha]

https://issues.redhat.com/browse/CRW-803