Problem with DNS resolution in kickstart post script

Solution Verified - Updated -

Issue

  • During kickstart in the post section, the actual network configuration is written including a resolv.conf with the production network information. Those nameservers are not accessible during kickstart.
  • The final two steps of the kickstart do the following within the chrooted environment:
%post# Start post install kernel options update
[...]
wget "http://satellite5-server.example.com/cblr/svc/op/ks/profile/RHEL6-x86_64:2:INTERNAL-ORG" -O /root/cobbler.ks
wget "http://satellite5-server.example.com/cblr/svc/op/trig/mode/post/profile/RHEL6-x86_64:2:INTERNAL-ORG" -O /dev/null
%end
  • Those two commands are not run successfully because the nameservers in the chrooted environment are not accessible. This delays the kickstart process by 2 times the resolve timeout and additionally the cobbler.ks will be empty.

Environment

  • Red Hat Satellite 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.