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

Remove preflight checks as part of crc daemon #3093

Closed
praveenkumar opened this issue Mar 30, 2022 · 7 comments
Closed

Remove preflight checks as part of crc daemon #3093

praveenkumar opened this issue Mar 30, 2022 · 7 comments

Comments

@praveenkumar
Copy link
Member

praveenkumar commented Mar 30, 2022

Why do we have preflight checks for crc daemon this is always block in case crc daemon is started as standalone process after #3088 and #3072. Also crc daemon doesn't need to have any checks before it can run.

After following PR merge if dev member try to do following then it will fail to debug the daemon api.

> .\crc.exe daemon
INFO Checking if running in a shell with administrator rights
INFO Checking Windows 10 release
INFO Checking Windows edition
INFO Checking if Hyper-V is installed and operational
INFO Checking if crc-users group exists
INFO Checking if current user is in Hyper-V Admins group
INFO Checking if Hyper-V service is enabled
INFO Checking if the Hyper-V virtual switch exists
INFO Found Virtual Switch to use: Default Switch
INFO Checking if vsock is correctly configured
INFO Checking if daemon task is installed
exit status 1
@gbraad
Copy link
Contributor

gbraad commented Mar 30, 2022

the daemon starts slowly due to these checks; the tray has a delay of 4 to 6 seconds for this. after the removal of these preflights for the daemon we can check if the tray can start quicker,

@cfergeau
Copy link
Contributor

crc daemon doesn't need to have any checks before it can run.

Why? When is the daemon going to validate the OS is setup properly for crc use?

@praveenkumar
Copy link
Member Author

crc daemon doesn't need to have any checks before it can run.

Why? When is the daemon going to validate the OS is setup properly for crc use?

@cfergeau do we really need that? Daemon is separate process and doesn't need any setup to run. It is not depend on preflight to run correctly right? crc setup and crc start require preflight check because these command depend on it not the setup like other subcommand version, oc-env ..etc?

@gbraad
Copy link
Contributor

gbraad commented Mar 30, 2022

the daemon can run independent of a crc setup. the actual check happens when you perform a crc start.

@cfergeau
Copy link
Contributor

Yes, this is the background info that was missing, that the needed checks will be ran as part of crc start anyway.

@cfergeau
Copy link
Contributor

After following PR merge if dev member try to do following then it will fail to debug the daemon api.

Fwiw, the right skip option can be set for this. This is not a very compelling reason for removing the checks ;)

@praveenkumar
Copy link
Member Author

It is removed with 4582375

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

3 participants