Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1377294 - Subnet page, ipv4 network prefix field should be above the netmask field
Summary: Subnet page, ipv4 network prefix field should be above the netmask field
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Networking
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Ondřej Pražák
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 11:43 UTC by Sanket Jagtap
Modified: 2019-09-26 15:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:47:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
fields in the subnet form (18.68 KB, image/png)
2017-08-16 13:50 UTC, Ondřej Pražák 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18514 0 None None None 2017-02-15 10:05:58 UTC

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
Note You need to log in before you can comment on or make changes to this bug.