Open andikaopp opened 1 year ago
@andikaopp you might be facing the issue #3812, can you please try the following commands and then run crc setup
again? This should fix the crcDaemon task not in Running but in Ready
state problem.
PS> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
PS> crc.exe setup --log-level debug
from the logs, the Admin Helper service is also not running, can you verify from the Windows Service Manager if a service named "Red Hat OpenShift Local Admin Helper" is installed?
"Red Har Openshift Local Admin Helper" was installed and run in my services
when i run crc setup
again after running above command, showing like this
@andikaopp Can you please share the o/p of: crc setup --log-level debug
debug logs should have a bit more information as to why even after daemon and admin-helper running its again asking for a reboot
C:\Users\andik>crc setup --log-level debug
DEBU CRC version: 2.25.0+97705a
DEBU OpenShift version: 4.13.6
DEBU Podman version: 4.4.4
DEBU Running 'crc setup'
INFO Using bundle path C:\Users\andik\.crc\cache\crc_hyperv_4.13.6_amd64.crcbundle
INFO Checking minimum RAM requirements
DEBU Total memory of system is 16890978304 bytes
INFO Checking if current user is in crc-users and Hyper-V admins group
DEBU Running '(Get-LocalGroupMember -Group 'crc-users').Name'
DEBU Checking current user is in the 'crc-user' group
DEBU group members: ANDIKAOPP\andik
DEBU Running '(Get-LocalGroupMember -SID 'S-1-5-32-578').Name'
DEBU Checking current user is in the 'Hyper-v Administrators' group
DEBU group members: ANDIKAOPP\andik
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if C:\Users\andik\.crc\cache\crc_hyperv_4.13.6_amd64.crcbundle exists
DEBU C:\Users\andik\.crc\cache\crc_hyperv_4.13.6_amd64.crcbundle exists
INFO Checking if the daemon task powershell script is present
INFO Checking if the daemon task is installed
DEBU Running 'Get-ScheduledTask -TaskName crcDaemon'
DEBU Running '(Get-ScheduledTask -TaskName "crcDaemon").Version'
INFO Checking if the daemon task is running
DEBU Running '(Get-ScheduledTask -TaskName "crcDaemon").State'
INFO Checking admin helper service is running
DEBU Running '(Get-Service crcAdminHelper).Status'
DEBU Get "http://unix/version": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Make sure you installed crc using the Windows installer and performed required reboot
Do you have an application firewall installed?
It seems the admin-helper service is running, but the named pipe is not accessible, which should not happen, can you please also use this tool: https://learn.microsoft.com/en-us/sysinternals/downloads/accesschk and run the following command (unfortunately i couldn't find a way to get the permissions using powershell cmdlets)
PS> .\acceesschk64.exe \pipe\crc-admin-helper
it should give you the following o/p: (members of the crc-users
should have RW access to the named pipe)
i have been trying that command, but i have some errors like this
my question: where can i get the path of \pipe\crc-admin-helper
? because from this error like not found the spesific file
this is a named pipe path, and it is not present in the filesystem, the Red Hat OpenShift Local Admin Helper
service should create this, so make sure if the service is running. (you can see all the named pipes on the system using ls \\.\Pipe\
)
am unable to reproduce these issues on a clean windows 11 installation, have you tried uninstalling and re-installing the MSI, and see if that helps..
@andikaopp are you using crc alone or with Podman desktop and the OpenShift Local extension?
@andikaopp can you please try the latest (v2.33.0
) release and see if that fixes your issues
Hello everyone, I had the same error. I solved it by following these steps:
General information
crc setup
before starting it (Yes)? but failsCRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
Success setup and showing icon tray openshift
Actual
Error:
Setup failed. Error: 'Make sure you installed crc using the Windows installer and performed required reboot '. Please restart.
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.