If the network is up outside the chroot, is it safe to assume the network should be available inside of a chroot? I switch to alt-f2 during the subiquity init and can do an 'ip a' and see the ip and ping 'yahoo.com' and do a 'wget https://google.com'. Is there anything I should run that would help you to know if this is an issue on my side?
/var/crash/1672818234.937400103.install_fail.crash contains the IP address that eno1 received when it made it's dhcp call. The routes are present in the file as well. It may be a network issue, but not because my local net isn't passing out addresses or isn't able to access the internet.
I'm going to attach the user-data (autoinstall) I'm using to repro this. We're running this on an Intel NUC which probes our nic using the e1000e module.
If the network is up outside the chroot, is it safe to assume the network should be available inside of a chroot? I switch to alt-f2 during the subiquity init and can do an 'ip a' and see the ip and ping 'yahoo.com' and do a 'wget https:/ /google. com'. Is there anything I should run that would help you to know if this is an issue on my side?
/var/crash/ 1672818234. 937400103. install_ fail.crash contains the IP address that eno1 received when it made it's dhcp call. The routes are present in the file as well. It may be a network issue, but not because my local net isn't passing out addresses or isn't able to access the internet.
I'm going to attach the user-data (autoinstall) I'm using to repro this. We're running this on an Intel NUC which probes our nic using the e1000e module.