Bug 1304713
Summary: | Entering invalid value for Floating IP gateway isn't caught | ||
---|---|---|---|
Product: | Red Hat Quickstart Cloud Installer | Reporter: | Thom Carlin <tcarlin> |
Component: | Installation - RHELOSP | Assignee: | Dylan Murray <dymurray> |
Status: | CLOSED ERRATA | QA Contact: | Dave Johnson <dajohnso> |
Severity: | medium | Docs Contact: | Dan Macpherson <dmacpher> |
Priority: | unspecified | ||
Version: | 1.0 | CC: | bthurber, cchase, dymurray, jmatthew, 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:59 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 |
Description
Thom Carlin
2016-02-04 12:52:20 UTC
Steps to Reproduce, 4. should include: Problem occurs in step 2D. Configure Overcloud in "Enter network blocks to assign to the overcloud for private networking and floating IP addresses." section (e.g. Floating IP Network is set to 192.168.253/24 and Floating IP Network Gateway is set outside that range: 192.168.0.254) https://github.com/fusor/fusor/pull/863 Added validations for floating IP gateway to be on the subnet of the floating ip network. Should show warnings if: - subnet is invalid - gateway ip address is invalid - gateway ip does not belong to the subnet of the network. Verified in QCI 1.2. Now says "must belong to subnet ip_network/24". Additionally, see "this is an invalid ip address" and "This is an invalid CIDR notation."192.168.253.254 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 |