Bug 1377294

Summary: Subnet page, ipv4 network prefix field should be above the netmask field
Product: Red Hat Satellite Reporter: Sanket Jagtap <sjagtap>
Component: NetworkingAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Ondřej Pražák <oprazak>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: bbuckingham, jcallaha, oprazak, sghai
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:47:20 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:
Attachments:
Description Flags
fields in the subnet form none

Description Sanket Jagtap 2016-09-19 11:43:00 UTC 
Description of problem:
This is for ipv4 , there is some irregularity with the validation of Netmask field and there is a validation error when we enter correct netmask , and it's gone, when the correct network prefix is entered.

Version-Release number of selected component (if applicable):
Build: Satellite 6.3 snap1.0

How reproducible:


Steps to Reproduce:
1.Go to Subnets page 
2.Create new subnet
3.Fill in the network address ((Observe the validation error)
4.Enter the prefix

Actual results:
There should be no validation error.

Expected results:
The prefix field should be above netmask field as the netmask is auto filled with reference to the n/w prefix.

Additional info:
I feel , there should be no need of prefix , if we have a netmask field, either of one field is enough.
Comment 2 Ondřej Pražák 2017-02-15 10:05:55 UTC 
Created redmine issue http://projects.theforeman.org/issues/18514 from this bug
Comment 3 Satellite Program 2017-02-22 21:09:06 UTC 
Upstream bug assigned to chrobert
Comment 4 Satellite Program 2017-03-01 15:09:34 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18514 has been resolved.
Comment 5 Ondřej Pražák 2017-08-16 13:50:50 UTC 
Created attachment 1314155 [details]
fields in the subnet form

Verified.

6.3.0 snap 11
Comment 6 Bryan Kearney 2018-02-21 16:43:07 UTC 
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-2018:0336
Comment 7 Bryan Kearney 2018-02-21 16:47:20 UTC 
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-2018:0336
Comment 8 Satellite Program 2018-02-21 16:51:07 UTC 
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-2018:0336