Description
During crc setup
, if hyperv needs to be installed, the system will need to be rebooted (as this is when hyperv gets enabled/installed). Similarly, the user will need to log out/log in for group membership to take effect.
At the moment, during the preflights, even if these checks/fixes returned errors, we keep going and try to figure out which switch is being used by hyperv, which requires hyperv to be installed/the user to be part of the hyperv admin group, so it will be failing.
What I'd expect instead is:
- run hyperv installation preflight check/fix
- run group membership preflight check/fix
3.1) if any of these 2 failed, instruct the user that they will need to reboot and to run crc setup again
3.2) if they both succeeded, run the other preflight checks/fixes (at the moment, the only other check is the hyperv network switch one).
Ideally, for 1 and 2, we'd be able to differentiate between "error which will be fixed by a reboot" and "unrelated error", we don't have that level of detail right now
And ideally, for 3.1), we'd be able to ask the user if they want to reboot now, and to resume crc setup ourselves after the reboot.
Activity