Foreman » Installer

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1110838
Description of problem:
When running the capsule installer in $some_configuration with DNS/DHCP, the config file located in '/var/named/dynamic/' seems to get generated without an IP address being associated with the hostname. The resulting install fails due to named being incorrectly configured/not starting.

Version-Release number of selected component (if applicable):

Satellite-6.0.3-RHEL-7-20140612.1

How reproducible:

Steps to Reproduce:
1. Run a capsule install with DNS and DHCP options, something like

export FORWARDERS=$(for i in $(cat /etc/resolv.conf |grep nameserver|awk '{print $2}'); do echo --dns-forwarders $i;done)

capsule-installer --parent-fqdn "qe-blade-05.idm.lab.bos.redhat.com" --dns "true" $FORWARDERS --dns-interface eth1 --dns-zone rhq.lab.eng.bos.redhat.com --dhcp "true" --dhcp-interface eth1 --tftp true --puppet "true" --puppetca "true" --register-in-foreman "true" --foreman-oauth-key "MhWrbms2BTXwBLHXH4ekXKRoUVPxVkAz" --foreman-oauth-secret "XpMwUtBQS2MHanQ4URaXkf8CC4e3Er7d" --pulp-oauth-secret "EHx82SprUPcpVMTE2fu4iGEUMH6vH4PE" --certs-tar "mgmt6.rhq.lab.eng.bos.redhat.com-certs.tar" --pulp "true"

2. Observe failure
3. Open the dynamic named file (in this case '/var/named/dynamic/db.rhq.lab.eng.bos.redhat.com') and view the hostname line at the bottom.

Actual results:

@ IN NS mgmt6.rhq.lab.eng.bos.redhat.com.

mgmt6.rhq.lab.eng.bos.redhat.com. IN A

Expected results:

@ IN NS mgmt6.rhq.lab.eng.bos.redhat.com.

mgmt6.rhq.lab.eng.bos.redhat.com. IN A xxx.xxx.xxx.xxx

(where xxx.xxx.xxx.xxx is the IP address)

Additional info:

Interestingly - and possibly a suitable workaround for now - if user manually edits this file and re-runs the install command above, install seems to be successful.