-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.9
-
Quality / Stability / Reliability
-
None
-
None
-
None
-
Critical
-
None
-
x86_64
-
None
-
None
-
Rejected
-
None
-
None
-
If docs needed, set a value
-
None
-
None
-
None
-
None
-
None
Description of problem: No console available.
Version-Release number of selected component (if applicable):
CodeReady Containers version: 1.38.0+659b2cbd
OpenShift version: 4.9.12 (bundle installed at C:\Program Files\CodeReady Containers\crc_hyperv_4.9.12.crcbundle)
How reproducible: It is stably reproducible.
Steps to Reproduce:
1. $Env:Path += ";C:\app\redhat_crc"
2. Execute C:\app\redhat_crc\crc-windows-amd64.msi
3. crc setup
4. crc start --pull-secret-file 'C:\app\redhat_crc\pull-secret.txt' --nameserver 8.8.8.8 --log-level debug
5. crc oc-env
6. & crc oc-env | Invoke-Expression
7. oc login -u developer -p 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
Actual results:
Unable to connect to the server: read tcp 127.0.0.1:57439->127.0.0.1:443: wsarecv: An existing connection was forcibly closed by the remote host.
Expected results:
Access to the console, as developer and as kubeadmin.
Additional info:
I need CRC for my development work (Java/Qaurkus/Fuse) for a client and spent all day today installing CRC on my Windows PC. I read countless blog entries, disabled the firewall and ran the installation several times. Always with the same result. I can't access the console. I don't know what to do anymore and would be glad if you could help me.