[BUG] When initialization failed, impossible to recover and move forward with the extension

[slemeur]

General information

• OS: macOS
• Did you run crc setup before starting it (Yes/No)? No
• Running CRC on: Laptop

CRC version

CRC version: 2.27.0+71615e
OpenShift version: 4.13.12
Podman version: 4.4.4

CRC status

DEBU CRC version: 2.27.0+71615e
DEBU OpenShift version: 4.13.12
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
crc does not seem to be setup correctly, have you run 'crc setup'?

CRC config

- consent-telemetry                     : no
- preset                                : microshift

Host Operating System

ProductName:        macOS
ProductVersion:     14.0
BuildVersion:       23A344

Steps to reproduce

1. Failed installation of OpenShift Local.
2. Try to go to settings > resources

Expected

User is able to restart the process

Actual

Impossible to move forward in the flow. The bog button redirects to the settings.

On the dashboard no action button is given either.

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.

[anjannath]

If we go the Settings > Extension > OpenShift Local and then Disable the extension and then enable it again, the Initialize button on the dashboard re-appears.

Maybe in the dashboard on the OpenShift Local tile, we can mention this workaround, to disable and enable the extension from the Settings > Extension > OpenShift Local (this also helps when the detection checks fails and we want the detection checks to run again)

[deboer-tim]

That's not bad as a last resort, but it's like telling someone to try rebooting if the CRC cli fails. Couldn't we check and reset the state after any installation attempt (success or failure)?