rubygem-staypuft: Creating a new subnet from within the deployment enforces specifying gateway for networks with no DHCP server.
Steps to reproduce:
1. Start creating a deployment, advance to "network configuration" page (#2)
2. Click on "New subnet" and select "No existing DHCP" for DHCP server.
3. Fill the network address/name, don't fill the "Gateway" fied and click on "Create subnet".
The subnet is not created. There's a validation on the gateway field: "can't be blank and is invalid".
Setting the gateway should be optional, so the validation should prevent blank field.
Not sure if this is a bug, the behavior was specified by the trello card: https://trello.com/c/Lpn3Ce4Y/126-subnets-define-enhancements-for-staypuft-specific-subnet-form
(In reply to Imre Farkas from comment #1)
> Not sure if this is a bug, the behavior was specified by the trello card:
The card is incorrect if it says that a gateway is required. The user/admin needs to be able to specify a gateway if it exists, but should not require one.
Note that if the gateway is not specified then DEFROUTE should be set to "no" in the associated ifcfg file.
(In reply to Chris Dearborn from comment #4)
> Note that if the gateway is not specified then DEFROUTE should be set to
> "no" in the associated ifcfg file.
DEFROUTE gets set to NO on all devices except the Public-API network. If the Public-api network does not exist on a host, it defaults to the Provisioning network.
Able to create the network without specifying the gateway.
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.