Description of problem: staypuft-installer is taking the host gateway as the DHCP gateway by default, while it should take the IP address of the selected interface. Version-Release number of selected component (if applicable): # rpm -qa | grep staypuft foreman-installer-staypuft-0.0.20-1.el6ost.noarch ruby193-rubygem-staypuft-0.1.4-1.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. Run staypuft-installer 2. Select the internal interface for provisioning 3. Actual results: The 'DHCP Gateway' is set to the 'Host Gateway' value. Expected results: The 'DHCP Gateway' should be set to the 'IP address' value. Additional info: The default behavior is: # staypuft-installer Please select NIC on which you want Foreman provisioning enabled: 1. eth1 2. eth0 ? 2 Networking setup: Network interface: 'eth0' IP address: '192.168.200.1' Network mask: '255.255.255.0' Network address: '192.168.200.0' Host Gateway: '10.35.7.254' DHCP range start: '192.168.200.2' DHCP range end: '192.168.200.254' DHCP Gateway: '10.35.7.254' DNS forwarder: '10.35.255.14' Domain: 'staypuft.com' Foreman URL: 'https://slimer.staypuft.com' Configure networking on this machine: y
Fixed in 0.0.23
Verified with rhel-osp-installer-0.0.25-5.el6ost.noarch The default gateway is according the selected NIC - In this case eth1 IP is 192.168.0.1 and the DHCP Gateway is accordingly: Please select NIC on which you want Foreman provisioning enabled: 1. eth1 2. eth0 ? 1 Networking setup: Network interface: 'eth1' IP address: '192.168.0.1' Network mask: '255.255.255.0' Network address: '192.168.0.0' Host Gateway: '10.8.31.254' DHCP range start: '192.168.0.2' DHCP range end: '192.168.0.254' DHCP Gateway: '192.168.0.1' DNS forwarder: '10.10.160.2' Domain: 'lab.eng.rdu2.redhat.com' Foreman URL: 'https://staypuft.lab.eng.rdu2.redhat.com' NTP sync host: '0.rhel.pool.ntp.org' Configure networking on this machine: ✓ Configure firewall on this machine: ✓
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1003.html