Bug 1102706
| Summary: | staypuft-installer does not provide separate options for host gateway and dhcp routers | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Mike Burns <mburns> |
| Component: | rubygem-staypuft | Assignee: | Marek Hulan <mhulan> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 (RHEL 7) | CC: | ajeain, dnavale, jslagle, mburns, mhulan, sclewis |
| Target Milestone: | ga | ||
| Target Release: | 5.0 (RHEL 7) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-installer-staypuft-0.0.18-1.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
internal only, no doc text needed
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-04 18:32:26 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 1108362 has been marked as a duplicate of this bug. *** This is fixed in upstream since 0.0.18 Verified: foreman-installer-staypuft-0.0.18-1.el6ost.noarch
Now there's one more option and that is the DHCP gateway (as per below):
Network interface
IP address
Network mask
Network address
Host Gateway
DHCP range start
DHCP range end
DHCP Gateway
DNS forwarder
Domain
Foreman URL
Set this host networking
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 |
Description of problem: In the case where the foreman host acts as both the gateway and foreman server, the current options for setting the gateway are insufficient. There is only 1 option for gateway [see additional info]. If you leave option 12 enabled (configure this host networking), you end up with a non-functional foreman. This means that currently a user must make 2 runs of staypuft-installer in order to configure both the dhcp server and the host networking. The first run with the gateway for Foreman and "set this host networking" true. The second with the gateway==Foreman's ip address and "set this host networking" false. The only other option is to run once, then manually fix the configuration of one or the other. When foreman also acts as the gateway, you need to have a separate entry for "Host Gateway" and "DHCP Gateway". This will allow a user to separately specify both it's own gateway and the gateway it provides for other clients in the network. Version-Release number of selected component (if applicable): foreman-installer-staypuft-0.0.13-2.el6ost.noarch How reproducible: always Steps to Reproduce: 1.configure foreman machine also as a gateway 2.run staypuft-installer 3. Actual results: end up with dhcp providing invalid gateway -or- end up with foreman using an invalid gateway -or- end up manually configuring one of the above -or- end up running staypuft-installer twice (or more) Expected results: single run of staypuft-installer with everything configured Additional info: Current networking setup: Network interface: 'eth0' IP address: '192.168.223.2' Network mask: '255.255.255.0' Network address: '192.168.223.0' DHCP range start: '192.168.223.3' DHCP range end: '192.168.223.254' Gateway: '192.168.223.254' DNS forwarder: '192.168.122.1' Domain: 'staypuft.local' Foreman URL: 'https://foreman.staypuft.local' Set this host networking: ✓