Divine C

i clicked `restart` button from the screenshot mentioned in my above comment.. i received below error again ``` 0s Normal SuccessfulCreate replicaset/workspace027a7a2667034873-5486b546c4 Created pod: workspace027a7a2667034873-5486b546c4-gwdzp 0s Normal Scheduled pod/workspace027a7a2667034873-5486b546c4-gwdzp Successfully...

logs of workspace pod failing couple of times (reloaded the page) and then succeeding at the end (after page reload) ``` dchelladura-a01:vtapbotservice divine$ kubectl get events -n divine-chelladurai-che-pmjg9u -w LAST...

i will observe the logs in the pods you have mentioned and monitor it @tolusha but , i did some analysis and this is my observation of my current issue...

@tolusha i was able to analyze and gather more information on the issue. i have 1 master node and 3 worker nodes in my k8s cluster (workernode1, workernode2, workernode3). when...

@tolusha i'm stuck with this issue now. please share your feedback on this.

@tolusha i have used `nodeSelector`, i can see my `PV` and `workspace` container running in same `workerNode` even after deletion and re-creation of `workspace`. but i still face the same...

@tolusha i have used `nodeSelector`. Now both my `workspace` and `pv` are always getting created in same `workernode` even after mutliple restarts. But still i'm facing this issue. i'm receiving...

@AObuchow @tolusha i receive below error message after adding `per-workspace` in my `devfile.yaml`. chectl version ``` chectl/0.0.20220809-next.c9f4ba1 darwin-x64 node-v16.13.2 ``` below is my devfile.yaml ``` schemaVersion: 2.1.0 metadata: name: cbfsel-repo...

@tolusha i'm using `quay.io/devfile/devworkspace-controller:v0.14.1`

@tolusha i `scaled down` and `scaledup` by `che-operator` deployment. The `che-operator` deployment was successful. but it didnot update the resources in `devworkspace-controller` namespace.