[BUG] crc network not reachable

[sinamna]

General information

• OS: Linux ( Ubuntu )
• Hypervisor: KVM
• Did you run crc setup before starting it (Yes/No)? yes
• Running CRC on: VM

CRC version

CRC version: 2.30.0+b6532a
OpenShift version: 4.14.3
Podman version: 4.4.4

CRC status

DEBU CRC version: 2.30.0+b6532a
DEBU OpenShift version: 4.14.3
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
CRC VM:          Running
OpenShift:       Unreachable (v4.14.0-0.okd-2023-12-01-225814)
RAM Usage:       360.6MB of 16.75GB
Disk Usage:      19.58GB of 32.68GB (Inside the CRC VM)
Cache Usage:     25.31GB
Cache Directory: /home/ubuntu/.crc/cache

CRC config

- consent-telemetry                     : no
- cpus                                  : 6
- host-network-access                   : true
- memory                                : 16384
- network-mode                          : user
- preset                                : okd

Host Operating System

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Steps to reproduce

1. set host-network-access to true and network-mode to user
2. run crc setup
3. run crc start

Expected

crc instance should be running and reachable

Actual

openshift is unreachable and can't ssh into vm (based on method described in wiki)

Logs

running crc start --log-level debug result in this

DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/ubuntu/.crc/machines/crc/id_ecdsa /home/ubuntu/.crc/cache/crc_okd_libvirt_4.14.0-0.okd-2023-12-01-225814_amd64/id_ecdsa_crc]
DEBU SSH command results: err: ssh: handshake failed: read tcp 127.0.0.1:33324->127.0.0.1:2222: read: connection reset by peer, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: read tcp 127.0.0.1:33324->127.0.0.1:2222: read: connection reset by peer
 - sleeping 1s
DEBU retry loop: attempt 77
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/ubuntu/.crc/machines/crc/id_ecdsa /home/ubuntu/.crc/cache/crc_okd_libvirt_4.14.0-0.okd-2023-12-01-225814_amd64/id_ecdsa_crc]
DEBU SSH command results: err: ssh: handshake failed: read tcp 127.0.0.1:33340->127.0.0.1:2222: read: connection reset by peer, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: read tcp 127.0.0.1:33340->127.0.0.1:2222: read: connection reset by peer
 - sleeping 1s
DEBU RetryAfter timeout after 78 tries
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
DEBU (crc) DBG | time="2024-01-06T14:42:56Z" level=debug msg="Closing plugin on server side"
Failed to connect to the CRC VM with SSH -- virtual machine might be unreachable: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: read tcp 127.0.0.1:39012->127.0.0.1:2222: read: connection reset by peer

in the same time crc-daemon shows this

Jan 06 14:42:44 crc-1 crc[26459]: 2024/01/06 14:42:44 tcpproxy: for incoming conn 127.0.0.1:32960, error dialing "192.168.127.2:22": connect tcp 192.168.127.2:22: no route to host
Jan 06 14:42:47 crc-1 crc[26459]: 2024/01/06 14:42:47 tcpproxy: for incoming conn 127.0.0.1:32966, error dialing "192.168.127.2:22": connect tcp 192.168.127.2:22: no route to host
Jan 06 14:42:51 crc-1 crc[26459]: 2024/01/06 14:42:51 tcpproxy: for incoming conn 127.0.0.1:33324, error dialing "192.168.127.2:22": connect tcp 192.168.127.2:22: no route to host
Jan 06 14:42:55 crc-1 crc[26459]: 2024/01/06 14:42:55 tcpproxy: for incoming conn 127.0.0.1:33340, error dialing "192.168.127.2:22": connect tcp 192.168.127.2:22: no route to host

[praveenkumar]

@sinamna I can see you are running crc in VM which mean nested virtualization setup (which we don't test) any reason to running it on VM instead directly on that host?

[sinamna]

@praveenkumar We didn't have an available host. isn't nested virtualization supported at all?

[praveenkumar]

@praveenkumar We didn't have an available host. isn't nested virtualization supported at all?

@sinamna we don't have any hardware to test this setup and also linux BM test happen using fedora/centos-stream (not ubuntu).