dstack icon indicating copy to clipboard operation
dstack copied to clipboard

[Bug]: Force remove of busy instance leaves instance running

Open r4victor opened this issue 1 year ago • 1 comments

dstack version

master

Python version

3.11

Host OS

macOS 13.4

Host Arch

ARM

What happened?

  1. Run a job.
  2. Stop the job.
  3. While the instance is busy, remove it with --force.
  4. The CLI says the instance is removed but it stays ready.

CLI logs

(venvt) ➜  my_dstack_public git:(master) ✗ dstack pool remove serious-bat-1-0 --
force
 Pool name  default-pool

Remove instance 'serious-bat-1-0'? [y/n]: y
Instance 'serious-bat-1-0' removed
(venvt) ➜  my_dstack_public git:(master) ✗ dstack pool ps                     
 Pool name  default-pool

 INSTANCE    BACKEND  REGION    RESOURCES   SPOT  PRICE      STATUS  CREATED    
 serious-b…  gcp      us-west4  2xCPU,      yes   $0.009104  ready   4 mins ago 
                                8GB, 100GB                                      
                                (disk)

Server logs

No response

Runner logs

No response

Additional Information

No response

r4victor avatar Feb 28 '24 05:02 r4victor

This issue is stale because it has been open for 30 days with no activity.

peterschmidt85 avatar Mar 30 '24 01:03 peterschmidt85

This issue was closed because it has been inactive for 14 days since being marked as stale.

peterschmidt85 avatar Apr 25 '24 01:04 peterschmidt85