[BUG] Impossible to restart Microshift instance

[slemeur]

I have made the update of OpenSHift Local from 2.28 to 2.30.

Then I tried to restart my microshift environnement (which I created the day before)

General information

• OS: macOS
• Podman Desktop 1.7.0-next

CRC version

# Put `crc version` output here

CRC status

# Put `crc status --log-level debug` output here

CRC config

# Put `crc config view` output here

Host Operating System

# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

Steps to reproduce

Expected

Actual

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.

[slemeur]

It's also impossible after deleting the previous instance to do create a new one

[slemeur]

From the CLI
$ crc start Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": dial unix /Users/slemeur/.crc/crc-http.sock: connect: connection refused

[praveenkumar]

From the cli can you try $ crc setup and then start?

[slemeur]

yes that's what I ended up doing - but the user will never understand that

[slemeur]

is there anyway, we can handle that for the user?

[praveenkumar]

Have to check with extension side but when Cannot reach daemon API: Get "http://unix/api/version" means crc setup required.

[gbraad]

@jeffmaury @dgolovin FYI. i do not think this will happen often, but needs to be resolved.

note: this is part of the update flow.

[slemeur]

Cannot reach daemon API: Get "http://unix/api/version" means crc setup required.

Then why not adding it in the error message? As a user I like error messages, but I prefer how to work around them :)