Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693907 - Creating subnet allows "slash notation"/"Network prefix" to be entered twice.
Summary: Creating subnet allows "slash notation"/"Network prefix" to be entered twice.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Provisioning
Version: 6.3.2
Hardware: x86_64
OS: Linux
medium
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-29 01:55 UTC by Amaani S Karimi
Modified: 2019-03-30 01:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4017471 None None None 2019-03-29 02:34:02 UTC

Description Amaani S Karimi 2019-03-29 01:55:05 UTC
Description of problem:

When entering the network address for a subnet, the system does not reject it with a "slash notation" at the end (CIDR Format), and when you use the network prefix field as well, it doubles it up.

As an example, this "x.x.x.x/24" entered in the network address, and /24 as the network prefix.  This resulted in a Subnet of "x.x.x.x/24/24" being displayed.

It displayed "x.x.x.x/24/24" as the subnet - which is clearly not valid.

It should allow x.x.x.x in one field, and then /24 in the other - but not
in both and should throw an alert or highlight it red if the user tries to give slash notation in the network address.

Version-Release number of selected component (if applicable):

Red Hat Satellite 6.3.2

How reproducible:

100%

Actual results:


It displayed "x.x.x.x/24/24" as the subnet - which is clearly not valid.

Expected results:

It should allow x.x.x.x in one field, and then /24 in the other - but not
in both and should throw an alert or highlight it red if the user tries to give slash notation in the network address.


Note You need to log in before you can comment on or make changes to this bug.