General information
- OS: Windows 10 Enterprise 1909
- Hypervisor: Hyper-V
- Did you run
crc setup
before starting it (Yes/No)? Yes
CRC version
# Put the output of `crc version`
``` crc version: 1.5.0+e1c8fb8 OpenShift version: 4.2.14 (embedded in binary)
## CRC status
```bash
# Put the output of `crc status`
``` CRC VM: Running
OpenShift: Running (v4.2.14-x86_64)
Disk Usage: 13.06GB of 32.2GB (Inside the CRC VM)
Cache Usage: 12.73GB
Cache Directory: C:\Temp\.crc\cache
## CRC config
```bash
# Put the output of `crc config view`
```- http-proxy: http://<USERNAME>:<SECRET>@<IP>:8080
- https-proxy: http://<USERNAME>:<SECRET>@<IP>:8080
- no-proxy: localhost,.cluster.local,.svc,.testing,10.128.0.0/14,127.0.0.1,172.30.0.0/16,192.168.126.0/24,api-int.crc.testing,api.crc.testing,etcd-0.crc.testing,localhost
## Host Operating System
```bash
# 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: <REDACTED>
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.18363 N/A Build 18363
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner: <REDACTED>
Registered Organization: <REDACTED>
Product ID: 00329-00000-00003-AA523
Original Install Date: 13/02/2020, 14:44:49
System Boot Time: 15/02/2020, 10:29:51
System Manufacturer: HP
System Model: ProLiant m710x Server Cartridge
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~3000 Mhz
BIOS Version: HP H07, 26/02/2019
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-gb;English (United Kingdom)
Input Locale: N/A
Time Zone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory: 16,253 MB
Available Physical Memory: 2,700 MB
Virtual Memory: Max Size: 19,197 MB
Virtual Memory: Available: 5,140 MB
Virtual Memory: In Use: 14,057 MB
Page File Location(s): C:\pagefile.sys
Domain: <REDACTED>
Logon Server: \\<REDACTED>
Hotfix(s): 9 Hotfix(s) Installed.
[01]: KB2693643
[02]: KB4534132
[03]: KB4513661
[04]: KB4516115
[05]: KB4517245
[06]: KB4521863
[07]: KB4537759
[08]: KB4538674
[09]: KB4532693
Network Card(s): 5 NIC(s) Installed.
[01]: Mellanox ConnectX-3 Pro Ethernet Adapter
Connection Name: Embedded LOM 1 Port 1
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[02]: Mellanox ConnectX-3 Pro Ethernet Adapter
Connection Name: Embedded LOM 1 Port 1 2
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[03]: Mellanox Virtual Miniport Driver
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[04]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (Default Switch)
DHCP Enabled: No
IP address(es)
[01]: 192.168.137.1
[05]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (crc)
DHCP Enabled: Yes
DHCP Server: 11.0.65.70
IP address(es)
[01]: 11.14.133.95
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
### Steps to reproduce
CRC is configured with External Virtual Switch (crc) and cluster is started successfully
1. Configure Proxy Wide on the Cluster with custom CA as detailed [here](https://docs.openshift.com/container-platform/4.2/networking/enable-cluster-wide-proxy.html)
2. Create a new project "dv-project"
3. Create secret to pull from registry
> oc create secret docker-registry dv-pull-secret \
> --docker-server=registry.redhat.io \
> --docker-username=CUSTOMER_PORTAL_USERNAME \
> --docker-password=CUSTOMER_PORTAL_PASSWORD \
> --docker-email=EMAIL_ADDRESS
>
> oc secrets link builder dv-pull-secret
> oc secrets link builder dv-pull-secret --for=pull
>
4. Create a new project "dv-project" and install the Data Virtualization Operator from OperatorHub
5. oc get pods -n dv-project
6. oc describe pod <POD>
### Expected
The newly operator pod started successfully using the proxy configuration
### Actual
The newly operator pod failed to start with error in pulling image. "error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp: lookup registry.redhat.io on 10.88.0.8:53: no such host"
### Logs
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 29m default-scheduler Successfully assigned dv-project/dv-operator-6d664d649d-rtw8r to crc-q4zfq-master-0
Normal Pulling 27m (x4 over 29m) kubelet, crc-q4zfq-master-0 Pulling image "registry.redhat.io/fuse7-tech-preview/dv-rhel7-operator:1.5"
Warning Failed 27m (x4 over 29m) kubelet, crc-q4zfq-master-0 Failed to pull image "registry.redhat.io/fuse7-tech-preview/dv-rhel7-operator:1.5": rpc error: code = Unknown desc = error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp: lookup registry.redhat.io on 10.88.0.8:53: no such host
Warning Failed 27m (x4 over 29m) kubelet, crc-q4zfq-master-0 Error: ErrImagePull
Warning Failed 24m (x21 over 29m) kubelet, crc-q4zfq-master-0 Error: ImagePullBackOff
Normal BackOff 4m16s (x110 over 29m) kubelet, crc-q4zfq-master-0 Back-off pulling image "registry.redhat.io/fuse7-tech-preview/dv-rhel7-operator:1.5"
Thanks
There might be more bugs to iron out with proxy support, I wanted to check if I can reproduce your bug, but hit/fixed issue #1019 first.