Comment 5 for bug 1800724

I believe this to be the ONLY corner case that fell-out from the fix that stopped the surprising, automatic removal of 'current' models when they no longer exist.

What is happening here is that you have destroyed your current model but did not switch from it. In fact you have switched into it which is a no-op.. Even your reference in description has this extract:

(clients) jenkins@juju-001b34-osci-18:~/tools/0/charm-test-infra$ juju switch auto-osci-sv07:auto-osci-sv07
auto-osci-sv07:admin/auto-osci-sv07 *(no change)*

So your workaround here is valid but even switching to any other model and back again would have given you an error. Here is what I get: https://pastebin.ubuntu.com/p/RNsFMcpndk/

I will fix the check in switch commands that determines if the requested switch is no-op and will make it behave. Will propose shortly against 2.4 branch with the intention to forward-port to develop.