Well, what I see is a system which is having hard time to access a HTTP URL. Again, describe all steps you have performed in order to verify that your installation medium is available to the provisioned node. Like connecting to the machine via SSH or console and performing some commands (nslookup, ping, telnet, curl/wget)…
I still stuck with opensuse installation. I am able to ping the installation media and able to wget from foremen server. It is actually failing at n/w interface configuration point at kernal level installation. is there a way to increase the dhcp timeout? also can you point out to documentation that lists step by step for opensuse provisioning. Please help and it will be greatly appreciable.
I don’t use Suse so I can’t help, you better try Suse community and then modify your template. Ideally, send us a patch into community-templates repo, add a DHCP timeout parameter or something like that if you resolve your issue.
I can confirm that slow DHCP servers are very often culprit of a problem.
After further research, my patch solves a different thing. In your case, your DHCP server (what’s that by the way) have some problems with parsing the default DHCP client ID which is sent by OS. So you set it to MAC address to get around it. But I believe this will work out of box for most users, it’s some misconfiguration on your server probably. Is this Ethernet or Infiniband?