Bug #2285
closedValidation doesn't prevent "invalid address" error when creating subnets
Description
When adding a subnet in the provisiong and having accidently a whitespace in front of the Network: eg " 192.168.16.0" instead of "192.168.16.0" I get this error:
Oops, we're sorry but something went wrong
x invalid address
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.
Back
ArgumentError
invalid address
app/models/subnet.rb:72:in `new'
app/models/subnet.rb:72:in `cidr'
app/models/subnet.rb:38:in `to_label'
app/views/subnets/index.html.erb:17:in `_app_views_subnets_index_html_erb___1480953890_70168276658080_0'
app/views/subnets/index.html.erb:14:in `_app_views_subnets_index_html_erb___1480953890_70168276658080_0'
lib/foreman/thread_session.rb:31:in `clear_thread'
It appears when doing this for the first subnet.
I can add other subnets but I can not modify them, since this page shows where I would expect to see the already defined subnets
Updated by Dominic Cleal about 12 years ago
- Subject changed from problem with creating subnets to Validation doesn't prevent "invalid address" error when creating subnets
- Category set to Web Interface
Updated by Joseph Magen almost 12 years ago
- Status changed from New to Assigned
- Assignee set to Joseph Magen
Updated by Joseph Magen almost 12 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100