Devfile mode: the run command process isn't killed, before starting the debug command process, if 'restart' attribute is set as false #3738
Labels
area/devfile-spec
Issues or PRs related to the Devfile specification and how odo handles and interprets it.
kind/bug
Categorizes issue or PR as related to a bug.
Pre requisite knowledge :
the restart attribute, as illustrated here , enables (when set as true) or disbles (when set as false) the retriggering of a project's build cycle inside the deployed container when
odo push
is used and newly added or edited files are pushed inside the running app container.Case when
restart
attribute to set as trueUsing a nodejs project while using the nodejs devfile from the default registry
https://github.com/odo-devfiles/registry/blob/78f685b7476791d9e45a0c9d6bbb8398b93d0216/devfiles/nodejs/devfile.yaml
if you see the logs here, it is ensured that the running commands are forcefully killed before the debug command is started.
Case when
restart
attribute to set as falseUsing a quarkus project while using this devfile.
if you see the logs here, the process started by the run command is not killed before starting the debug command process.
This leads to an error as the port occupied from the run command is not released for the debug command to start properly.
BUT
When I set the restart attribute as true, the ongoing processes are killed before the debug command starts. Check the logs...
The text was updated successfully, but these errors were encountered: