Description of problem:
Currently we are unable to create subnets from the UI using the "Infrastructre" --> "subnets"--> "new subnet" button.
2016-03-02 13:13:31 [app] [I] Failed to save: Subnet domains is invalid, Subnet domains is invalid
2016-03-02 13:13:31 [app] [I] Rendered subnets/_fields.html.erb (19.8ms)
2016-03-02 13:13:31 [app] [I] Rendered common/_edit_habtm.html.erb (39.1ms)
2016-03-02 13:13:31 [app] [I] Rendered taxonomies/_loc_org_tabs.html.erb (20.5ms)
2016-03-02 13:13:31 [app] [I] Rendered subnets/_form.html.erb (216.0ms)
2016-03-02 13:13:31 [app] [I] Rendered subnets/new.html.erb (218.0ms)
2016-03-02 13:13:31 [app] [I] Completed 200 OK in 454ms (Views: 203.0ms | ActiveRecord: 37.6ms)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a new subnet with valid values
Unable to create new subnet via "Infrastructre" --> "subnets"--> "new subnet" button.
Should be able to create new subnet via "Infrastructre" --> "subnets"--> "new subnet" button.
Workaround: Currently using the "import subnet" button found on the smart-proxy dropdown helps identify subnet and create one for us.
I was able to create a subnet with:
network address: 192.168.121.0
network mask: 255.255.255
I am, however, unable to delete it in the UI. Doing so, results in an error indicating:
Error: test (192.168.121.0/24) is used by example.com
This is bug, you can't select domains on new subnet creation. If you don't choose any domain, it works. After it's persisted you can edit the subnet and assign domain. There's already a PR waiting to be re-reviewed and merged.
And just for the record, you can't delete subnet if it's used by some host so the error that Brad mentions is expected behavior. You'd have to disassociate the subnet from host prior subnet deletion.
Moving to POST since upstream bug http://projects.theforeman.org/issues/13711 has been closed
Applied in changeset commit:46eec8ba4163a8f237b3189f43d2f873a2267288.
we can now create the subnet ( with domain info) at the time of creation itself.
VERIFIED with Sat6.2-SNAP3-compose1
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.