If your CORD Pod fails to build, look in the output and find the corresponding section below to help troubleshoot the problem.

prereqs-common failures

Hardware Requirements

Make sure your hardware requirements reflect the ones reported here: Requirements

CPU Quantity Check

The Head node must have at least 12 CPU cores.  Verify that your system has adequate CPU resources.


The nodes must support KVM virtualization on the CPUs being used.  You may have to turn it on in the firmware (BIOS, EFI, etc.) of your system.  Sometimes a firmware update is required to support this if the system is older.

If you're trying to implement this in a "nested virtualization" environment, the virtualization system must support this and have it turned on for your VM. 

Systems that support nested virtualization:

Systems that lack nested virtualization:

DNS Lookup Check

The nodes must be able to look up hosts on the internet, to download software, VM images, etc. This verifies that your DNS is working properly using `dig`.  if this step fails, try running the playbook again, and if it still doesn't work, check that your DNS settings are working correctly.

DNS Global Root Connectivity Check

A DNS server is run on the head node to resolve internal DNS for the pod, and for non-pod domains it will makes requests to the global DNS root servers. If this step fails, verify that you do not have a firewall that is blocking outgoing DNS requests.

HTTP Download Check

This verifies that you can download files from the internet.   If this fails, make sure you don't have a proxy or other system blocking network traffic.

There is experimental support for running behind a proxy.

HTTPS Download Check

The same as the HTTP check above, but over HTTPS.  If this fails but the HTTP succeeds, check for a proxy, and that the time on the node is accurate. 

dns-configure failures

Check that VM's can be found in DNS

This likely means that something has gone wrong either with the connectivity or setup of the DNS server, or with the client configuration.  Verify that /etc/resolv.conf on all the nodes is using the IP address of the head node's default interface as the DNS server.