Crc: [BUG] Networking issues on Windows 10 Hyper-V

[mark-buckwell]

General information

• OS: Windows Version 1903
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Yes

CRC version

# Put `crc version` output here
version: 1.0.0-rc.0+34371d3
OpenShift version: 4.2.0-0.nightly-2019-09-26-192831 (embedded in binary)
 ```
## CRC status
```bash
# Put `crc status` output here
ERRO Error occurred: error: CreateFile C:\Users\mark\.crc\machines\crc\kubeconfig: The system cannot find the file specified.
 - exit status 1

CRC config

# Put `crc config view` output here
<empty>

Host Operating System

# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows
Host Name:                 DESKTOP-DL6MEKN
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Product ID:                00330-80000-00000-AA680
Original Install Date:     09/08/2019, 08:20:51
System Boot Time:          19/10/2019, 14:31:12
System Manufacturer:       Dell Inc.
System Model:              XPS 15 9570
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~2208 Mhz
BIOS Version:              Dell Inc. 1.13.0, 22/08/2019
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-gb;English (United Kingdom)
Time Zone:                 (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory:     32,503 MB
Available Physical Memory: 22,375 MB
Virtual Memory: Max Size:  37,367 MB
Virtual Memory: Available: 23,898 MB
Virtual Memory: In Use:    13,469 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-DL6MEKN
Hotfix(s):                 8 Hotfix(s) Installed.
                           [01]: KB4515871
                           [02]: KB4503308
                           [03]: KB4508433
                           [04]: KB4515383
                           [05]: KB4515530
                           [06]: KB4516115
                           [07]: KB4521863
                           [08]: KB4517389
Network Card(s):           5 NIC(s) Installed.
                           [01]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection
                                 Status:          Media disconnected
                           [02]: Killer Wireless-n/a/ac 1535 Wireless Network Adapter
                                 Connection Name: WiFi
                                 DHCP Enabled:    Yes
                                 DHCP Server:     N/A
                                 IP address(es)
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch) 2
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.18.88.209
                                 [02]: fe80::f168:3e4b:2cce:4476
                           [04]: Microsoft Network Adapter Multiplexor Driver
                                 Connection Name: Network Bridge
                                 DHCP Enabled:    Yes
                                 DHCP Server:     N/A
                                 IP address(es)
                           [05]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (New Virtual Switch)
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.161.1
                                 IP address(es)
                                 [01]: 192.168.161.124
                                 [02]: fe80::ed0b:7b43:90d0:f1f0
                                 [03]: fdbf:3d40:3851:10:4518:a22:10e:4511
                                 [04]: 2a02:c7f:126d:f400:25b5:d6d2:52bb:ba88
                                 [05]: fdbf:3d40:3851:10:ed0b:7b43:90d0:f1f0
                                 [06]: 2a02:c7f:126d:f400:ed0b:7b43:90d0:f1f0
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

1. crc setup
2. crc start
   HyperV default interface only picked up IPv6 address and not IPv4
3. crc stop
4. Change default switch to external switch in HyperV
   HyperV external interface picked up both IPv4 and IPv6 address
   ssh failed - missing file from machine
5. crc stop
6. Copied .crc\cache\crc_hyperv_4.2.0-0.nightly-2019-09-26-192831\id_rsa_crc to .crc\machines\crc\id_rsa
7. crc start
   cannot update nameserver
8. crc stop
9. crc start -n "8.8.8.8"
   failed again

Actual

PS C:\Users\mark> crc setup INFO Checking if running as normal user INFO Caching oc binary INFO Unpacking bundle from the CRC binary INFO Check Windows 10 release INFO Hyper-V installed INFO Is user a member of the Hyper-V Administrators group INFO Does the Hyper-V virtual switch exist
Setup is complete, you can now run 'crc start' to start a CodeReady Containers instance
PS C:\Users\mark> crc start
*******************************************************************************************************************************************************************************************************INFO Does the Hyper-V virtual switch exist ? Image pull secret [? for help] ******************************************************************************************************* Shutting Down 0% [ ] ******* Shutting Down 0% [ ] **************************************************************************************************************************************************************************************************************************

INFO Extracting bundle: crc_hyperv_4.2.0-0.nightly-2019-09-26-192831.crcbundle ...
INFO Creating CodeReady Containers VM for OpenShift 4.2.0-0.nightly-2019-09-26-192831...
INFO Verifying validity of the cluster certificates ... ERRO Error occurred: unknown error occurred ERRO Error occurred: unknown error occurred ERRO Error occurred: unknown error occurred PS C:\Users\mark> crc stop ****************************************

---

---

---

---

INFO Check Windows 10 release
INFO Hyper-V installed and operational
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
INFO Starting CodeReady Containers VM for OpenShift 4.2.0-0.nightly-2019-09-26-192831...
ERRO Error occurred: Failed to connect to the crc VM with SSH
PS C:\Users\mark> crc stop
Stopping CodeReady Containers instance... this may take a few minutes
CodeReady Containers instance stopped
PS C:\Users\mark> crc start
INFO Checking if running as normal user
INFO Checking if oc binary is cached
INFO Check Windows 10 release
INFO Hyper-V installed and operational
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
INFO Starting CodeReady Containers VM for OpenShift 4.2.0-0.nightly-2019-09-26-192831...
INFO Verifying validity of the cluster certificates ...
INFO Will run as admin: add dns server address to interface vEthernet (Default Switch)
ERRO Error occurred: Nameserver not successfully set
ERRO Error occurred: Error running post start: Nameserver not successfully set
PS C:\Users\mark> crc stop
Stopping CodeReady Containers instance... this may take a few minutes
CodeReady Containers instance stopped
PS C:\Users\mark> crc -n "8.8.8.8" start
INFO Checking if running as normal user
INFO Checking if oc binary is cached
INFO Check Windows 10 release
INFO Hyper-V installed and operational
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
INFO Starting CodeReady Containers VM for OpenShift 4.2.0-0.nightly-2019-09-26-192831...
INFO Verifying validity of the cluster certificates ...
INFO Adding 8.8.8.8 as nameserver to Instance ...
INFO Will run as admin: add dns server address to interface vEthernet (Default Switch)
ERRO Error occurred: Nameserver not successfully set
ERRO Error occurred: Error running post start: Nameserver not successfully set

Logs

https://gist.github.com/mark-buckwell/c900814ffb9c6095921fafd2bdb32c78

[gbraad]

ERRO Error occurred: Nameserver not successfully set

This relates to the DNS override not being possible as the device name likely does not match.

Change default switch to external switch in HyperV
HyperV external interface picked up both IPv4 and IPv6 address

You can not modify the network at the moment. We rely on using the Default Switch to provide DHCP and NAT functionality.

In future versions we might allow the creation of a 'crc' named Virtual Switch according to your own settings, see #722. But at the moment this is not possible. Please use the Default Switch as-is.

[gbraad]

Note: running crc -n "8.8.8.8" start has no effect, as the issue is with the DNS that runs inside the VM. This is needed to allow the use of the crc.testing domain.

[mark-buckwell]

Thanks - I suspected only the default switch can be used but I think there is a defect in Windows as it only supplies an IPv6 address on the default interface. I have deleted the device so it recreates the default interface again but no joy.

I assume the ssh key not being copied is down to not obtaining an IPv4 address the first time.

[gbraad]

Ahve you ever used Docker for Windows with the LCOW feature?

[mark-buckwell]

Yes, I have in the past and VirtualBox. I have been trying to clean the remnants...

[gbraad]

The LCOW feature breaks the networking stack. This was a known issue, but there is no workaround AFAIK. I do not know what I did, but it got fixed eventually ... but it only did so after being on the Insider fast ring (been over half a year at least).

[mark-buckwell]

Groan I will close this and one day I might be able to fix Windows

Thanks

[mark-buckwell]

I may have found a solution here https://github.com/docker/for-win/issues/1166

The interface metric for WiFi needs to be changed to a number lower than all other interfaces

 > Set-NetIPInterface -InterfaceAlias 'WiFi' -InterfaceMetric 5

and DHCP was disabled for IPv4

 > Set-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' -dhcp enable

I deleted all interfaces except WiFi and Bluetooth. Then rebooted to recreate the vEthernet

Then it should look like this

 > Get-NetIPInterface | Sort-Object -Property InterfaceMetric -Descending

ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore
------- --------------                  ------------- ------------ --------------- ----     --------------- -----------
43      vEthernet (Default Switch)      IPv4                  1500             300 Enabled  Connected       ActiveStore
43      vEthernet (Default Switch)      IPv6                  1500             300 Enabled  Connected       ActiveStore
1       Loopback Pseudo-Interface 1     IPv6            4294967295              75 Disabled Connected       ActiveStore
1       Loopback Pseudo-Interface 1     IPv4            4294967295              75 Disabled Connected       ActiveStore
18      Bluetooth Network Connection    IPv6                  1500              65 Disabled Disconnected    ActiveStore
18      Bluetooth Network Connection    IPv4                  1500              65 Enabled  Disconnected    ActiveStore
19      Local Area Connection* 10       IPv4                  1500              25 Enabled  Disconnected    ActiveStore
9       Local Area Connection* 12       IPv6                  1500              25 Disabled Disconnected    ActiveStore
9       Local Area Connection* 12       IPv4                  1500              25 Enabled  Disconnected    ActiveStore
19      Local Area Connection* 10       IPv6                  1500              25 Disabled Disconnected    ActiveStore
2       WiFi                            IPv6                  1500               5 Enabled  Connected       ActiveStore
2       WiFi                            IPv4                  1500               5 Enabled  Connected       ActiveStore

[mark-buckwell]

I then had to copy the ssh key and kubeconfig manually to the machine directory

[mark-buckwell]

I am able to login using

oc login -u developer -p developer https://api.crc.testing:6443

but cannot use developer/developer via the console login

[mark-buckwell]

Progress - I can create a new project.

oc new-project node-red-deploy

but not get to a git repository which I assume means I still have a network problem

 > oc new-app --name=node-red-deploy --docker-image=nodered/node-red
warning: Cannot find git. Ensure that it is installed and in your path. Git is required to work with git repositories.
W1019 20:16:37.346032    3796 dockerimagelookup.go:236] container image registry lookup failed: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 172.30.0.10:53: server misbehaving
error: unable to locate any local docker images with name "nodered/node-red"

The 'oc new-app' command will match arguments to the following types:

  1. Images tagged into image streams in the current project or the 'openshift' project
     - if you don't specify a tag, we'll add ':latest'
  2. Images in the Docker Hub, on remote registries, or on the local Docker engine
  3. Templates in the current project or the 'openshift' project
  4. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to point to an image that does not exist yet.

See 'oc new-app -h' for examples.

[mark-buckwell]

I can login using kubeadmin but it says I need to Update the cluster OAuth configuration to allow others to log in.
Something to look at tomorrow. But progress.

[mark-buckwell]

It starts but I get this error - any ideas?

WARN Failed Public dns query: ssh command error:
command : host -R 3 quay.io
err     : Process exited with status 1
output  : ;; connection timed out; no servers could be reached
 :

[gbraad]

Promising!

The quay.io issue is related to external DNS. In some cases this does not
get properly provided to the VM. It might have the local nameserver (from
the Windows ICS infra), but it is not responding. This might either be
because of a VPN (turn it off for now) or just a glitch. if the last, you
can use the -n option on start as you did before, like crc start -n 8.8.8.8. This will provide an additional nameserver on start of the VM
which can be used to resolve external addresses.

On Sun, Oct 20, 2019 at 4:40 AM mark-buckwell [e-mail]
wrote:

It starts but I get this error - any ideas?

WARN Failed Public dns query: ssh command error:
command : host -R 3 quay.io
err : Process exited with status 1
output : ;; connection timed out; no servers could be reached
:

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/746?email_source=notifications&email_token=AAAAOZQIFITNRWGERBX7V7TQPNWCVA5CNFSM4JCQWL62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBX4IPA#issuecomment-544195644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZRVBA7SN5TB3XHFSLDQPNWCVANCNFSM4JCQWL6Q
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]

[mark-buckwell]

That solved the problem with the quay.io error on startup.

I can run through the workflow to deploy the image nodered/node-red and I now see the following event record.

Failed to pull image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1e8d5ad0ab034d02f8298079ce7ba14ba08ab20862e9c9181051705caa72e367": rpc error: code = Unknown desc = Error reading manifest sha256:1e8d5ad0ab034d02f8298079ce7ba14ba08ab20862e9c9181051705caa72e367 in quay.io/openshift-release-dev/ocp-v4.0-art-dev: unauthorized: access to the requested resource is not authorized

[gbraad]

to the requested resource is not authorized

Without further instructions it is hard to understand the issue, but it feels like this is outside the scope of CRC. If you have provided the pull-secret this should be handled this way. We handled the situation from bring setting up virtualization, starting the VM, setting network until the final deployment of the OpenShift cluster. Almost all user steps performed with oc against this cluster is part of the regular OpenShift usage.

[praveenkumar]

access to the requested resource is not authorized

@mark-buckwell This issue is mostly because of pull secret, did you try to get the latest one from https://cloud.redhat.com/openshift/install/crc/installer-provisioned here or you are using an older pull secret which you provided in the crc config?

[mark-buckwell]

Yes, I used the pull secret during the installation otherwise it would not start. I had to manually copy the ssh key and kubeconfig to get it to work though.

[cfergeau]

Since you initially had ssh communication issues with the VM, maybe the steps for adding the pull secret to the VM failed. I'd try crc delete && crc start

[gbraad]

I had to manually copy the ssh key

should not be needed and most likely indicate other issues

On Tue, Oct 22, 2019 at 4:08 PM Christophe Fergeau [e-mail]
wrote:

Since you initially had ssh communication issues with the VM, maybe the
steps for adding the pull secret to the VM failed. I'd try crc delete &&
crc start

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/746?email_source=notifications&email_token=AAAAOZSBFSJ5RKNCFWCCTBDQP2YIBA5CNFSM4JCQWL62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB44HLA#issuecomment-544850860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZTHO524GFDM5RIVJU3QP2YIBANCNFSM4JCQWL6Q
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]

[buckwem]

Thanks - I did try crc delete and manually removing the .crc directory to test at the weekend. I will try again this weekend when I get home to see if I did something incorrectly.

[mark-buckwell]

I have now retested.

1. I rancrc stop and crc delete then removed the .crc directory.
2. I then downloaded the latest version of code and pull secret. Unzipped and copied crc.exe to c:\windows
3. I checked the networking was correct - DHCP was enabled on IPv4 and IPv6. The WiFi interface for IPv4 and IPv6 was enabled with interface metric the lowest at 5
4. Then crc setup and crc start but that did not work.
5. I then copied i) id_rsa_crc in the cache to id_rsa in machines\crc and ii) kubeconfig from cache to machines\crc
6. I then restarted with crc start -n '8.8.8.8' to remove the quay.io error
7. I turned off the firewall to check that was not a problem

It restarted and the following was noted after logging in with kubeadmin:

1. developer/developer could not be used as per instructions
2. there was the error You are logged in as a temporary administrative user. Update the cluster OAuth configuration to allow others to log in. on login
3. The following event was recorded Failed to pull image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:82938332ae2b152615e88a46213940c23a3c30b01d3ede88cf6763a1a86a8c77": rpc error: code = Unknown desc = Error reading manifest sha256:82938332ae2b152615e88a46213940c23a3c30b01d3ede88cf6763a1a86a8c77 in quay.io/openshift-release-dev/ocp-v4.0-art-dev: unauthorized: access to the requested resource is not authorized is in the events

I did note the new release notes said it only works with Fall Creators Update v1709 and I am on v1903 May 2019. Hopefully this is all useful to you.

[buckwem]

@gbraad is what I am seeing related to another bug? is there a fix in the pipeline for v1903? (I can't see anything obvious on the Sprint 174)

[talat-shaheen]

I am also facing a similar issue (windows v1903).

Failed to pull image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:40b2971c4aa5ee9f477eecc7a55ae7b46f16a8469572ae690d210a60ebffbf82": rpc error: code = Unknown desc = Error reading manifest sha256:40b2971c4aa5ee9f477eecc7a55ae7b46f16a8469572ae690d210a60ebffbf82 in quay.io/openshift-release-dev/ocp-v4.0-art-dev: unauthorized: access to the requested resource is not authorized

Any update on the error?

[dubbrian]

Pulled latest crc for hyperv from red hat .
Seems like internal network in hyperv is ipv6 only. I was able to use powershell command to change vms network bridge to external after vm created and before before the crc script started it and can see in hyperv manager the assigned ipv4 and ipv6 addresses. I ran crc start in debug mode but it seems to get stuck so frequently. Is there any intention to fix this as I cant aee anyone getting this hyperv image to work? I had hope to abandon virtualbox but may have to reinstall it again to try that. I just upgraded to 16gb ram and 1tb as on my laptop so a bit frustrated. Learned far more about hyperv and powershell scripting than I wanted to. Windows 10 1903 and crc based on oc 4.2.8

[dubbrian]

PS C:\Users\dubbrian> systeminfo

Host Name: XXXXXXXX
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.18362 N/A Build 18362
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner: XXXXXXX
Registered Organization: XXXXXXXX
Product ID: 00331-10000-00001-XXXXXXX
Original Install Date: 11/07/2019, 14:23:59
System Boot Time: 05/12/2019, 19:11:18
System Manufacturer: Hewlett-Packard
System Model: HP EliteBook Folio 9470m
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~2601 Mhz
BIOS Version: Hewlett-Packard 68IBD Ver. F.73, 12/04/2019
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: 083c
Input Locale: en-ie;English (Ireland)
Time Zone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory: 16,247 MB
Available Physical Memory: 2,136 MB
Virtual Memory: Max Size: 24,951 MB
Virtual Memory: Available: 7,039 MB
Virtual Memory: In Use: 17,912 MB
Page File Location(s): C:\pagefile.sys
Domain: europe.ad.flextronics.com
Logon Server: \EUDUC005
Hotfix(s): 11 Hotfix(s) Installed.
[01]: KB4515871
[02]: KB4497727
[03]: KB4498523
[04]: KB4503308
[05]: KB4508433
[06]: KB4509096
[07]: KB4515383
[08]: KB4516115
[09]: KB4521863
[10]: KB4524569
[11]: KB4524570
Network Card(s): 6 NIC(s) Installed.
[01]: Intel(R) 82579LM Gigabit Network Connection
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[02]: Intel(R) Centrino(R) Advanced-N 6235 Driver
Connection Name: Wi-Fi
Status: Media disconnected
[03]: Bluetooth Device (Personal Area Network)
Connection Name: Bluetooth Network Connection
Status: Media disconnected
[04]: PANGP Virtual Ethernet Adapter
Connection Name: Ethernet 5
Status: Media disconnected
[05]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (Default Switch)
DHCP Enabled: No
IP address(es)
[01]: 192.168.162.81
[02]: fe80::3596:9989:9d0a:a96c
[06]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (External Virtual Switch)
DHCP Enabled: Yes
DHCP Server: 10.219.247.13
IP address(es)
[01]: 10.226.152.41
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
PS C:\Users\dubbrian>

[gbraad]

Seems like internal network in hyperv is ipv6 only

We only support people using the Default Switch or an external switch that
provides a DHCP server that hands out valid IPv4 addresses (named 'crc')

Is there any intention to fix this

Not sure what you mean 'this' refers to?

I can not really conclude from your issues what the steps were you have
taken for this.

On Fri, Dec 6, 2019 at 6:04 AM dubbrian [e-mail] wrote:

Pulled latest crc for hyperv from red hat .
Seems like internal network in hyperv is ipv6 only. I was able to use
powershell command to change vms network bridge to external after vm
created and before before the crc script started it and can see in hyperv
manager the assigned ipv4 and ipv6 addresses. I ran crc start in debug mode
but it seems to get stuck so frequently. Is there any intention to fix this
as I cant aee anyone getting this hyperv image to work? I had hope to
abandon virtualbox but may have to reinstall it again to try that. I just
upgraded to 16gb ram and 1tb as on my laptop so a bit frustrated. Learned
far more about hyperv and powershell scripting than I wanted to. Windows 10
1903 and crc based on oc 4.2.8

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/746?email_source=notifications&email_token=AAAAOZWUU4EUXZ2PTTXNAOLQXF3GNA5CNFSM4JCQWL62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGCJ4NY#issuecomment-562339383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZW4EQGMJPSMKWQAY4TQXF3GNANCNFSM4JCQWL6Q
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]

[gbraad]

@mark-buckwell Are you still experiencing the issue with "unauthorized: access to the requested resource is not authorized" ?

if so, please close the issue

[dubbrian]

@gbraad thanks so much for your reply. Apologies on the framing of my question, I was a bit tired and fed up. Was trying to run on default swtich and not geting ip v4 and thought that was an issue. I will create a crc external switch and try again.

Really appreciate your help and will fully drop all config info if i have further questions.

thanks
Brian

[dubbrian]

Adding the external network with name crc helped a lot. Suggest this maybe should be highlighted in docs. Getting further before crc hangs on dns issue. I will read up on that next. Thanks so much @gbraad for the crc steer

[mark-buckwell]

I performed a clean install of Windows 10 and the problem of not obtaining an IPv4 address did not happen.

However, the DNS lookup failed and after specifying crc start -n "8.8.8.8" the OpenShift cluster started without errors.

@gbraad I have closed on the basis this is a problem with Windows and Hyper-V not crc.

[gbraad]

it will be documented, but consider this an early release.

but yes, also the -n option is a known one... this happens on almost any
platform and we will improve this, as the way the library we use determines
this wrong on occasion. Thanks for the reminder.

On Sun, Dec 8, 2019 at 9:35 PM mark-buckwell [e-mail]
wrote:

Closed #746 https://github.com/code-ready/crc/issues/746.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/746?email_source=notifications&email_token=AAAAOZTEMHXAF4372DUL2PTQXTZZJA5CNFSM4JCQWL62YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVK4AWLI#event-2864188205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZU3BUEHIMZHDK6JUY3QXTZZJANCNFSM4JCQWL6Q
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]