Describe the bug
The RESTART_WORKSPACE action handler in Provider.tsx does not call checkSccMismatch() before restarting. Every other start/restart action (START_DEBUG_AND_OPEN_LOGS, START_IN_BACKGROUND, RESTART_DEBUG_AND_OPEN_LOGS) performs this check and logs a warning when the workspace was created with a different container SCC than what is currently configured.
This means a plain "Restart Workspace" on a workspace with an SCC mismatch will silently proceed without any warning, while all other start/restart actions warn the user.
Steps to reproduce
- Configure a cluster with a non-default SCC for workspace containers.
- Create a workspace.
- Change the SCC configuration.
- Use the kebab menu to select "Restart Workspace".
- Observe no warning is logged — contrast with "Open in Debug mode" or "Start in Background" which log a
console.warn.
Expected behavior
RESTART_WORKSPACE should call checkSccMismatch() and log a warning, consistent with all other start/restart actions.
Dashboard PR
eclipse-che/che-dashboard#1596
Describe the bug
The
RESTART_WORKSPACEaction handler inProvider.tsxdoes not callcheckSccMismatch()before restarting. Every other start/restart action (START_DEBUG_AND_OPEN_LOGS,START_IN_BACKGROUND,RESTART_DEBUG_AND_OPEN_LOGS) performs this check and logs a warning when the workspace was created with a different container SCC than what is currently configured.This means a plain "Restart Workspace" on a workspace with an SCC mismatch will silently proceed without any warning, while all other start/restart actions warn the user.
Steps to reproduce
console.warn.Expected behavior
RESTART_WORKSPACEshould callcheckSccMismatch()and log a warning, consistent with all other start/restart actions.Dashboard PR
eclipse-che/che-dashboard#1596