Description of problem: subnet mask can be set to any IP address like (255.1.2.3) valid masks are only 128.0.0.0, 192..., 224..., etc. Version-Release number of selected component (if applicable): Satellite-6.0.4-RHEL-6-20140829.0 [Sat6-GA-Snap7-Compose3] How reproducible: always Steps to Reproduce: 1. # hammer subnet create --name subnet_1 --network 140.20.1.0 --mask 255.1.2.3 Subnet created
Created redmine issue http://projects.theforeman.org/issues/7430 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/7430 has been closed ------------- Christine Fouant Applied in changeset commit:7af45f0986480143e96d141390579279d62e526a.
VERIFIED With Sat6.1 Beta snap2 so subnet mask validation happens. [root@xxxxx ~]# hammer -u admin -p changeme subnet create --name qe_libvirt_199 --network 192.168.105.0 --mask 255.1.2.3 /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT Could not create the subnet: Network mask is invalid [root@xxxxx ~]# hammer -u admin -p changeme subnet create --name qe_libvirt_199 --network 192.168.105.0 --mask 192.3.4.5 /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT Could not create the subnet: Network mask is invalid
Created attachment 991362 [details] subnet mask validation happens via UI
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592