Closed eliassal closed 1 year ago
I reran crc start --log-level debug
now crc goes through but not oc command which is in bold hereunder(I choose Y or N for Use insecure connections I get the same response) nor browsing console-openshift-console.apps-crc.testing
DEBU CRC version: 2.29.0+da5f55 DEBU OpenShift version: 4.14.1 DEBU Podman version: 4.4.4 DEBU Running 'crc start' DEBU Total memory of system is 15031246848 bytes DEBU No new version available. The latest version is 2.29.0 DEBU Checking file: C:\Users\salam.crc\machines\crc.crc-exist DEBU Running 'Hyper-V\Get-VM crc | Select-Object -ExpandProperty State' DEBU Checking file: C:\Users\salam.crc\machines\crc.crc-exist DEBU Copying 'C:\Users\salam.crc\cache\crc_hyperv_4.14.1_amd64\oc.exe' to 'C:\Users\salam.crc\bin\oc\oc.exe' DEBU Copying 'C:\Users\salam.crc\cache\crc_hyperv_4.14.1_amd64\podman.exe' to 'C:\Users\salam.crc\bin\oc\podman.exe' INFO Loading bundle: crc_hyperv_4.14.1_amd64... DEBU Checking file: C:\Users\salam.crc\machines\crc.crc-exist DEBU Running 'Hyper-V\Get-VM crc | Select-Object -ExpandProperty State' INFO A CRC VM for OpenShift 4.14.1 is already running Started the OpenShift cluster.
The server is accessible via web console at: https://console-openshift-console.apps-crc.testing
Log in as administrator: Username: kubeadmin Password: 3UqwP-uUz2z-4QvCz-3MqsN
Log in as user: Username: developer Password: developer
Use the 'oc' command line interface: PS> & crc oc-env | Invoke-Expression
PS> oc login -u developer https://api.crc.testing:6443 DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name ReleaseId).ReleaseId' DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID' PS C:\Users\salam> oc login -u developer https://api.crc.testing:6443 The server uses a certificate signed by an unknown authority. You can bypass the certificate check, but any data you send to the server could be intercepted by others. Use insecure connections? (y/n): y
WARNING: Using insecure TLS client config. Setting this option is not supported!
Unable to connect to the server: read tcp 127.0.0.1:50592->127.0.0.1:443: wsarecv: An existing connection was forcibly closed by the remote host. PS C:\Users\salam> oc login -u developer https://api.crc.testing:6443 The server uses a certificate signed by an unknown authority. You can bypass the certificate check, but any data you send to the server could be intercepted by others. Use insecure connections? (y/n): n**
error: The server uses a certificate signed by unknown authority. You may need to use the --certificate-authority flag to provide the path to a certificate file for the certificate authority, or --insecure-skip-tls-verify to bypass the certificate check and use insecure connections. PS C:\Users\salam>**
When I try to connect using firefox I get
And here using MS Edge
After waiting for 60 minutes, MS Edge displayed the login page but once I enter I get the following error
This looks like duplicate of https://github.com/crc-org/crc/issues/3898 one.
OK but what is the solution or fix? as in #3898 no solution only description of the issue as this one
Can you please le us know how to proceed and fix this problem in order to be able to progress in our setup? Thanks
Running CRC on: VM
We do not support running CRC from a VM. So, can you clarify if this runs as a VM on Hyper-V or as a VM inside a VM on Hyper-V ?
I can answer this from the info:
System Model: Virtual Machine
System Type: x64-based PC
It seems Windows is running as a Virtual Machine and therefore this is a nested virtualization which do not support, due to resource overhead and possible timing issues with different hypervisors. Closing as this can not be resolved.
Can you please le us know how to proceed and fix this problem in order to be able to progress in our setup?
As described in the documentation: https://crc.dev/crc/getting_started/getting_started/installing/#_minimum_system_requirements "physical CPU cores" are required. Please run this on your native hypervisor, without a nested setup.
yes it is a nested VM. OK I will. run another setup directly on hyper-V but I dont want the CRC VM be created in the C drive, how can this be done? I mean can let crc setup create the VM on another drive?
the VM has to exist on the WINDRIVE
, that is a hard requirement from the drivers we are using.
So if I change the CRC install drive location it will create the VM on the C drive? is my understanding is correct?
You might be able to move the harddisk file AFTER the start
to another drive, but initially it will have to create this as part of the USERPROFILE
location .crc/machines/crc/
.
Note: moving these files around is not a setup we will support or fix issues for.
OK, so many thanks got it. Anyway, some good news, I followed install instructions directly on a physical Hyper-V and was able to access https://console-openshift-console.apps-crc.testing/add/all-namespaces locally but when I try to access remotely, after updating my hosts file to point to the IP of the machine as follows 192.168.10.14 5console-openshift-console.apps-crc.testing I get the alerte in Firefox, I accept the risk, then I get
So is there any config to be able to access the we site remotely? Thanks again
Please read the documentation.
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
Be able to browse https://console-openshift-console.apps-crc.testing Be able to run oc login -u developer https://api.crc.testing:6443
Actual
For first link console-openshift-console.apps-crc.testing, I get
for 2nd link oc login -u developer https://api.crc.testing:6443 I get
Logs
Before gather the logs try following if that fix your issue I TRIED so many times
output of
crc start --log-level debug
at https://gist.github.com/eliassal/7de92c774cf396d5cd8042360ec97498