Red Hat Bugzilla – Bug 1304149
Unable to recover from certain bad values.
Last modified: 2016-09-13 12:25:52 EDT
Description of problem:
During hackathon we ran across an instance of a user entering bad values in fusor-installer, subsequent runs with correct values were not honored and machine was broken.
Steps to Reproduce:
1. Use an ISO install of RHCI
2. Enter the correct IP address, say 192.168.155.10
3. Enter all other IP related values incorrect as 18.104.22.168,
ensure ALL other entries are wrong, unsure which one causes the problem, set all to incorrect values.
4. Proceed with install and see NTP warning
5. Attempt to fix errors and enter 192.168.155.1 and other correct values for the environment.
See that the issue is not fixed and still broken.
The only additional information to add is that when you re-run fusor_installer and fix all the bad IP related values (with the exception of the IP Address which is correct) it will still report an NTP connectivity warning.
It never actually uses the new IP Address information that you just entered or restarts the networking on the system.
IP Settings used to reproduce:
3. IP address: 192.168.155.10
4. Hostname: sat61fusor.example.com
5. Network mask: 255.255.255.0
6. Network address: 22.214.171.124
7. Host gateway: 192.168.155.1
8. DHCP range start[[BR]]: 126.96.36.199
9. DHCP range end: 188.8.131.52
10. DHCP Gateway: 184.108.40.206
11. DNS forwarder: 220.127.116.11
14. NTP sync host: clock.redhat.com
This is because the DNS forwarder address is bad. We may want to add a forwarder check as we did for NTP to ensure that they entered a valid DNS server. It will be impossible to check until after networking is set up though.
Can you please re-test this. I'm having trouble getting stuck and reproducing this. It's possible with all the changes it's no longer possible.
If you can reproduce it can you please provide steps for input that gets you there?
Verified in QCI-1.0-RHEL-7-20160816.t.0
Ran procedure above and was able to recover.
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.