[BUG] During 'Delete' daemon reports 'stopping' status

[evidolob]

General information

• OS: Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Yes
• Running CRC on: Laptop

CRC version

2.18.0

During 'Delete' daemon reports 'stopping' status, it is visible from crc-extension, when delete performed from podman-desktop resource page, the state changed from off (stopped) to Stopping and then connection disappears from UI.

[slemeur]

Yes I've observed this too

[gbraad]

@slemeur Which platform did you see this?

So far, I was only able to see this on Windows as the interaction with the VM is slower.

[gbraad]

@anjannath can you test this maybe tomorrow if you also see this, and maybe where this happens in the codebase?

[anjannath]

on macOS (M1) i don't see this happening with standalone daemon.. to check i was fetching status from daemon with a sleep of 1sec, and when crc delete is run, status changes to Machine does not exist. Use 'crc start' to create it.

anjan@anath-mac podman-desktop % for i in {1..100}; do
curl --unix-socket ~/.crc/crc-http.sock http://crc/api/status; printf "\n"; sleep 1
done
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
{"CrcStatus":"Running","OpenshiftStatus":"Running","OpenshiftVersion":"4.12.13","DiskUse":4628959232,"DiskSize":16095641600,"RAMUse":958763008,"RAMSize":4097531904,"Preset":"microshift"}
Machine does not exist. Use 'crc start' to create it

i believe this transition of states is by design, if the delete process takes a while, it shows the detailed status, as when a delete is requested, it first stops the VM and then remove its definition from the hypervisor and delete the associated files.

this comes from

crc/pkg/crc/machine/sync.go

Line 166 in bb69afc

func (s *Synchronized) Status() (*types.ClusterStatusResult, error) {

[anjannath]

I tried the latest podman-desktop from main branch, and now we have to first Stop to be able to Delete

Without stopping delete is disabled..

After stopping delete becomes active..

[gbraad]

That is acceptable behavior. But when delete is clicked, you will see stopping before it shows deleting.

[anjannath]

That is acceptable behavior. But when delete is clicked, you will see stopping before it shows deleting.

On M1 also I had seen this before but not anymore, when trying to reproduce this today, i didn't see Stopping.