[Satellite 6] Provisioning fails with error "curl: (6) Could not resolve host: satellite.example.com: Unknown error"

Environment

• Red Hat Satellite or Capsule 6.x
• Red Hat Enterprise Linux

Issue

• Provisioning a host through Red Hat Satellite fails with something like:

  dracut-initqueue[595]: Warning: failed to fetch kickstart from http://satellite.example.com:8000/unattended/provision?token=aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaa
  

• Hitting the below error while provisioning a host from the Satellite/Capsule server:

  curl: (6) Could not resolve host: satellite.example.com: Unknown error
  

Resolution

• Make sure that the DNS server is able to resolve Satellite's fully qualified domain name:

    # host satellite.example.com 192.168.100.2
    Using domain server:
    Name: 192.168.100.2
    Address: 192.168.100.2#53
    Aliases: 
  
    satellite.example.com has address 192.168.100.2
  

• The DNS resolution can fail with the below error:

  # host satellite.example.com 192.168.100.2
  ;; connection timed out; trying next origin
  ;; connection timed out; trying next origin
  ;; connection timed out; trying next origin
  ;; connection timed out; no servers could be reached
  

• Make sure that the host being provisioned is able to connect to the dns server on port 53. Please note that the nc command is not available from dracut shell, so alternatively use:

  # ping satellite.example.com
  

  and if it returns output like:

  ping: satellite.example.com: Name or service not known
  

  Check the contents of /etc/resolv.conf on the host, and make sure they point to the correct DNS server:

  # cat /etc/resolv.conf
  

• If /etc/resolv.conf on the provisioned host is pointing to the Satellite server instead of the DNS server, then make sure that /etc/dhcp/dhcp.conf on the Satellite server have the followOnllying option pointing to the IP address of the correct DNS server rather than to the IP address of the Satellite server:

  option domain-name-servers 10.160.50.22;
  

  If this option needs to be modified, make sure to restart the DHCP service on the Satellite server after editing /etc/dhcp/dhcp.conf.

• Make sure that the DNS server has the correct DNS records for the Satellite (or Capsule) hostname resolution.

• Ensure the expected Host's interface to be used during booting has enabled Provision flag: Go to the Host, edit it, in Interfaces, click to edit the interface and check Provision flag.

For more KB articles/solutions related to Red Hat Satellite 6.x Provisioning Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Provisioning related Issues

Root Cause

Provisioning fails because the provision host is unable to resolve the Satellite's fully qualified domain name, and hence fails to fetch the kickstart file.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.