Description of problem: When the livecd is booted there's not a way to change networking information from the static values provided to custom values without doing manual network configuration. We're looking into using the staypuft installer to have an option to apply the networking information collected during install to the system that it will be installed on. currently this information only configures foreman and not linux networking. Version-Release number of selected component (if applicable): How reproducible: Needed Feature Steps to Reproduce: 1. Boot the livecd in an environment where 192.168.223.0/24 is not applicable 2. need to reconfigure the networking exists 3. Actual results: Expected results: boot livecd, prompted for networking install, select option to reconfigure system networking to match what's collected that the prompts, continue installation. Additional info:
The final option in the first part of the installer is whether or not to setup networking on the host. This should fulfill this requirement. Please reopen if this does not work as expected
This does not work as expected. I updated the networking information using the UI and started the install. The host's ip address did not get updated and the installation failed. the dhcp config seems to be generated partially from the passed network info and partially from the host's networking. DHCP failed to start because the dhcpd.conf file had a mix of two different sets of networking information in it. If the system networking information is going to be updated it needs to happen before the rest of the installation proceeds so that the host can be contacted on the passed networking information.
I've run this again and watch the results. The Host's ip does get set, later than I initially expected. Though dhcp does not start properly and the record for the host /etc/hosts does not get set properly
The issue here is that the ipaddress for the dhcp template is being populated by a fact. Either the network hasn't restarted before dhcp is updated or the facts are cached.
This also appears to have put the wrong A record in bind.
Fixed in upstream 0.0.19
We need a mechanism to preseed networking configuration before Staypuft is run.
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/RHBA-2014-1090.html