Bug 1304149
Summary: | Unable to recover from certain bad values. | ||
---|---|---|---|
Product: | Red Hat Quickstart Cloud Installer | Reporter: | John Matthews <jmatthew> |
Component: | fusor-installer | Assignee: | Jason Montleon <jmontleo> |
Status: | CLOSED ERRATA | QA Contact: | James Olin Oden <joden> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0 | CC: | jmontleo, joden, kdube, tsanders |
Target Milestone: | ga | Keywords: | Triaged |
Target Release: | 1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-13 16:25:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1321046, 1342594 |
Description
John Matthews
2016-02-03 01:47:22 UTC
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: 192.169.155.0 7. Host gateway: 192.168.155.1 8. DHCP range start[[BR]]: 192.169.155.11 9. DHCP range end: 192.169.155.250 10. DHCP Gateway: 192.169.155.1 11. DNS forwarder: 192.169.155.1 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. https://access.redhat.com/errata/RHEA-2016:1862 |