redhat-developer / vscode-openshift-tools

OpenShift extension for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-openshift-connector
MIT License
95 stars 60 forks source link

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

Open lgrossma opened 2 months ago

lgrossma commented 2 months ago

https://github.com/user-attachments/assets/de7915cb-077c-48fe-acce-e396ed0e928a

vrubezhny commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

@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)