Skip to content
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

Clicking on "Refresh Status" in CRC setup page results in indefinite loading #4413

Open
lgrossma opened this issue Sep 2, 2024 · 3 comments

Comments

@lgrossma
Copy link
Contributor

lgrossma commented Sep 2, 2024

Screen.Recording.2024-09-02.at.20.33.42.mov
@vrubezhny
Copy link
Contributor

vrubezhny commented Sep 3, 2024

For me it kook about 30 minutes to install and try starting the CRC cluster, which actually didn't succeeded:

$ crc status -o json
{
  "success": false,
  "error": "Cannot get machine state: unexpected libvirt status 3\n",
  "preset": ""
}

But the Refresh Status never hang up for me.
Yes. After the wizard was finished starting the CRC cluster (not successfully) it takes a while to complete for Refresh Status (about a minute or so), but then it returns to the Status page (so you can click any of its buttons again, including Refresh Status)

@lgrossma
Copy link
Contributor Author

lgrossma commented Sep 3, 2024

Yeah, the startup takes a long time even when starting the crc in terminal, but via terminal the crc start always ends with success for me while it fails sometimes in the extension.

@vrubezhny
Copy link
Contributor

@lgrossma When you see a startup failure, please attach the log from Openshift Local logs Output here. I expect some error to occur so the startup cannot succeed. I'm interested if your log contains any error statuses like:

{
  "success": false,
  "error": "...",
  ...
}

On indefinite loading after "Refresh Status" is clicked... I cannot reproduce the issue, nor get the effect you screened on you video (dropping the settings and sending it back to the CRC install/initialization wizard when "Back" is clicked during the refreshing...
The refresh actually invokes crc version + crc status then crc console --credentials, so when one of the first two commands hangs up it could result into an infinite loading... But I couldn't reproduce this on a normally working CRC cluster.
When I was trying it previously on a "problematic" CRC installation (it couldn't be started probably due to lack of available disk space) - refreshing was taking much longer, but still was finishing successfully (showing the stopped cluster)

vrubezhny added a commit to vrubezhny/vscode-openshift-tools that referenced this issue Sep 6, 2024
vrubezhny added a commit that referenced this issue Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants