Skip to content

GitLab

Closed
Created by Valentin Reis@vreisOwner

Kill config needs two calls when tasks are running.

If some tasks are running,

$ argo_nodeos_config --show_config

NO SEPARATE SERVICE_OS!

----- COMPUTE CONTAINER -----
-Name: testContainer
-Owner: fre (1000)
-Hardware threads(exclusive): 0
-Memory nodes(non exclusive): 0
-Tasks: 26533 26535 26536 26537
-Not balancing load
-Memory migration is enabled

We get an error 1 using $ argo_nodeos_config --clean_config=kill_content:true:

argo_nodeos_config[pid:10694]|ERROR: [user:1000] Trying to delete a container that still hosts some tasks

It fails, but does kill tasks:

$ argo_nodeos_config --show_config

NO SEPARATE SERVICE_OS!

----- COMPUTE CONTAINER -----
-Name: testContainer
-Owner: fre (1000)
-Hardware threads(exclusive): 0
-Memory nodes(non exclusive): 0
-Tasks:
-Not balancing load
-Memory migration is enabled

A second attempt will kill the container properly :

$ argo_nodeos_config --clean_config=kill_content:true
$ echo $?
0
$ _output/argo_nodeos_config --show_config

NO SEPARATE SERVICE_OS!
Edited by Valentin Reis