Bug 1589132

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/provisioning_guide/#Configuring_Networking-Configuring_Network_Services_for_PXE_Boot

Section Number and Name: 
~~~
The following is an example configuration command:

# satellite-installer --foreman-proxy-dhcp true \
--foreman-proxy-dhcp-gateway "192.168.140.1" \
--foreman-proxy-dhcp-interface "eth1" \
--foreman-proxy-dhcp-nameservers "192.168.140.2" \
--foreman-proxy-dhcp-range "192.168.140.10 192.168.140.110" \
--foreman-proxy-dhcp-server "192.168.140.2" \
--foreman-proxy-dns true \
--foreman-proxy-dns-forwarders "8.8.8.8; 4.4.4.4" \
--foreman-proxy-dns-interface "eth1" \
--foreman-proxy-dns-reverse "140.168.192.in-addr.arpa" \
--foreman-proxy-dns-server "192.168.140.2" \
--foreman-proxy-dns-zone "example.com" \
--foreman-proxy-tftp true
The satellite-installer script applies these configuration options and sets up the required network services. After the configuration completes, use the hammer proxy info command to verify these services on the chosen Capsule Server. In this example, we use satellite.example.com as the domain name of the Satellite Server’s integrated Capsule:

# hammer proxy info --name "satellite.example.com"
The output shows a list of enabled features, including DNS, DHCP, and TFTP:

Features:
    Pulp
    TFTP
    DNS
    DHCP
    Puppet
    Puppet CA
    Dynflow
    SSH
~~~

Describe the issue: 
If you do not use the  `--foreman-proxy-dhcp-managed true` parameter the dhcp package is not installed and the dhcp config is not created.

Suggestions for improvement: 
Add the parameter to the example and also explain its purpose
--foreman-proxy-dhcp-managed true
--foreman-proxy-dhcp-managed  DHCP is managed by Foreman proxy (current: false)

Additional information: 
No error message is displayed if the parameter is forgotten however DHCP config and package will not exist on the system.