-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] When initialization failed, impossible to recover and move forward with the extension #181
Comments
If we go the Maybe in the dashboard on the OpenShift Local tile, we can mention this workaround, to disable and enable the extension from the |
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)? |
General information
crc setup
before starting it (Yes/No)? NoCRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
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
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.The text was updated successfully, but these errors were encountered: