-
Notifications
You must be signed in to change notification settings - Fork 241
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
Virtual switch name needs to be localized for Windows 10 - 1803, eg. German install #579
Comments
It is not clear what is happening. It feels like an issue with ssh, but you confirm it is listening as endpoint. Let me examine this more closely after editing the description/report. It is hard to read as all is nested inside a code block. |
Thank you! The first thing I observed was that "crc setup" was looking for a Hyper-V "Default Switch". Because my computer is setup with German locals it only comes with "Standardswitch". So I created a "Default Switch". I tried all kinds of setup for this switch - external, internal, private. But I don`t get "crc setup" running with either of this options., Could this lead to the problems I described. I mean SSH port of the VM is listening and asks for a passowrd. So it is not clear for me what to test next. |
And even if after I switched to English local now I still have the wrong switch which is not changeable PS C:\Users\crc> (Hyper-V\Get-VMSwitch).Name |
@youwalther65 You already seem to have connectivity with the VM, that means, its not an issue with the virtual switch, i think its because of the SSH client in use, Did you turn on the openssh client provided by windows? if so could you try to start |
Thanks a lot . This helps. Still got some Errors but worked around them. SSH binary not found, using native Go implementation C:\Users\crc\RedHat\crc-windows-1.0.0-beta.3-amd64>crc oc-env C:\Users\crc\RedHat\crc-windows-1.0.0-beta.3-amd64>@for /f "tokens=*" %i IN ('crc oc-env') DO @call %i C:\Users\crc\RedHat\crc-windows-1.0.0-beta.3-amd64>oc login -u kubeadmin -p 78UVa-zNj5W-YB62Z-ggxGZ https://api.crc.testing:6443 C:\Users\crc\RedHat\crc-windows-1.0.0-beta.3-amd64>oc login -u kubeadmin -p 78UVa-zNj5W-YB62Z-ggxGZ https://api.crc.testing:6443 Login successful. You have access to the following projects and can switch between them with 'oc project ':
C:\Users\crc\RedHat\crc-windows-1.0.0-beta.3-amd64>oc whoami C:\Windows\System32\drivers\etc>type hosts Copyright (c) 1993-2009 Microsoft Corp.192.168.178.72 console-openshift-console.apps-crc.testing Is this as expected? |
what is? You should have DNS working from the default switch. |
This would never work, as this would come without DHCP functionality. It seems you are running "Version 1803 (April 2018 Update)" from the release ID... but your Switch is localized? I thoght they fixed this. Perhaps this is only in later releases. Can you run the update? |
Please test with the current version of your Windows installation. I have created an update version of the binary (without an embedded bundle). You can find it at: http://artifacts.ci.centos.org/minishift/crc/pr/595/windows-amd64/ |
Thx gbraad but still getting an error in pre-create check using your crc Version which I renamed to "crc-dev" Current switch Setup (I deleted "Default Switch" which I have created to avoid Breaking the pre-check) Name SwitchType NetAdapterInterfaceDescription Shared Private Here the debug ouput INFO Extracting bundle: crc_hyperv_4.1.11.crcbundle ... |
From the logs vswitch check passed! what is the o/p of |
The Default Switch from Windows can not be removed (he removed his previous internal switch called as Default Switch). From the output I see: 'Standardswitch', which sounds like the German for the default. It seems to fail in the create step ... (got missed due to the bodge OP applied earlier). I will also create an issue to |
Exactly, "Standardswitch" is the one which should be choosed during setup. |
I made a change for the create process too... It should now work. Please have a go. |
Get the new artifacts at: http://artifacts.ci.centos.org/minishift/crc/pr/595/windows-amd64/ |
No regressions on current versions of Windows. |
It works now !!! Thx a lot :-) |
Will this crc setup fix be integrated into final solution? |
@praveenkumar I tested that version first but it didn't work. in my search for a fix i came across this thread. I then tested the two older betas and the fix provided a few post above. I now got the RC version to run with this exe http://artifacts.ci.centos.org/minishift/crc/pr/693/windows-amd64/ I can only say that the RC version did not work for me, as if this fix is not part of the RC release. |
This comment has been minimized.
This comment has been minimized.
Please use the RC binary for testing. do NOT submit issues against PR binaries as they are only offered for short-term tests. |
This fix is part of the RC releases 75b417e Please clean your environment with a
Note: output of |
guys please, i started everything with the RC release, and i used the RC binary. I only started using the PR binary since it didn't work. But as you wish, just for you i do it a third time, so you will believe me. |
This is not begging you, but your analysis has been hard to follow as you combined several version over the course. The original report contained no information to point to this: #579 (comment) |
Yes, no worries. But it's also about the RC version. If the fix does not work in the RC verison, i guess you would also like to know that. |
This is at the moment all I care about, as I need to make sure there is no regression. Note: I am glad to receive a report about this, as it has been hard for us to test. This issue only occurs with certain 'older' versions of Windows 10, and only when the install is performed using a Windows 10 localized installation, and not the MUI. |
One of the known versions with this issue. More recent versions, like 1903 do not have a localized Default Switch. |
i tested my current binary, than downloaded the one from your link. can't even delete the old VM
|
company policy. not yet allowed to upgrade |
In the meantime, please share the result of the PowerShell command:
|
PowerShell does not like the Id flag. but without it works C:\Users\tschoenb
λ Get-VMSwitch | ForEach-Object { $_.Name }
Standardswitch |
|
This is the issue... and this is not related to the switch name, but likely with how the binary was produced. |
I saw the error as well, but could not wrap my head around what that means. I mean, it can't create the VM I guess. |
Actually, it can't seem to start |
Ok. Not sure if I can help you more with this. At least i know that this can perform the process, create and start the VM.
I can post the debug log from the dev version if that helps |
Did you get a prompt to allow connections when it was named |
I also thought about windows firewall and set a rule specifically for crc.exe to allow everything. But that never changed anything. Still i just tried what you suggested:
|
It might be the way the executable was built. Can you try http://artifacts.ci.centos.org/minishift/crc/pr/694/windows-amd64/ ? |
i am missing the correct bundle for that.
so for now i am just making a copy.
|
So since i am able to delete the VM i guess it works. Only problem is that i don't know where to get the correct RC bundle. |
no, the bundle copy didn't work
|
This release should be the same as the https://mirror.openshift.com/pub/openshift-v4/clients/crc/1.0.0-rc.0/ Perhaps your bundle does not extract since you got bundle set. Verify this with |
That's also odd. I always get an empty config
running the start command again. update will follow soon update: as shown above the bundle does not like the manually changed name. |
but this link also contains the nightly bundle. So the RC bundle just has a different name? |
Oh, my bad. This sync might not have happened yet. Anyway, I got the information I want. it seems to be related to the binary. I might get back to you, can you send me an email at gbraad@redhat.com or me@gbraad.nl so I can share files directly without having to talk over GitHUu issue comments. |
Alright, done. Thank you very much for your help. |
General information
crc setup
before starting it (Yes/No)? ???CRC version
The text was updated successfully, but these errors were encountered: