This problem still bites us. I’ve tried to play around with DHCP
settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail.
I’m happy about /any/ hint.
1) ip route seems ok, but what does your /etc/resolv.conf looks like?
2) could you try with 7.3.1611, 7.2.1511 is no longer supported.
Tru curl: (6) Could not resolve host: our.CentOS.mirror; Unknown error
/etc/resolv.conf is 100% ok once I am in the dracut emergency shell and name resolution works fine. However I don’t know how it looks at the time of the error message – that is during dracut-initqueue – and I have no idea how I could check that.
Unfortunateyl not. Due to special hardware (Infiniband, FPGA) and special lustre drivers we are currently bound to this specific release.
We have a special appliance attached and get the lustre driver from the appliance vendor to ensure maximum compatibility and maintenance. So https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/el7.3.1611/
unfortunately doesn’t apply to us.
An then there are still FPGA and Infiniband where the vendors of our hardware currently don’t support CentOS 7.3 (yet).