Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 708926

Summary: No format limit when input irregular static IPv4 address
Product: Red Hat Enterprise Linux 6 Reporter: cshao <cshao>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: apevec, gouyang, leiwang, mburns, moli, ovirt-maint, ycui, zdover
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.0.0-0.git2fb6530.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 19:15:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description cshao 2011-05-30 07:31:04 UTC
Description of problem:
No format limit when input irregular static IPv4 address in set static network interface.

Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-201105010

How reproducible:
100%

Steps to Reproduce:
1. Configure a static IPv4 address via network UI (e.g.10.66.9.73.19.12)
2. Select Apply button
3.
  
Actual results:
The wrong format IP address can be applied.

Expected results:
Should pop up Warning msg "Invalid IP Address".

Additional info:

Comment 2 cshao 2011-06-01 02:17:29 UTC
Change Version-Release to rhev-hypervisor-6.1-20110510.1

Comment 6 cshao 2011-07-14 08:01:26 UTC
Test version:
rhev-hypervisor-6.2-0.5.el6

When input irregular static IPv4 address, system pop-up warning msg "Invalid IP Address".
So change bug status to VERIFIED.

Comment 7 Zac Dover 2011-10-13 00:19:46 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, Red Hat Enterprise Virtualization Hypervisor would not inform you when you input an ill-formed static IPv4 address.

Red Hat Enterprise Virtualization now informs you when you input an ill-formed static IPv4 address.

Comment 8 Alan Pevec 2011-10-25 12:35:32 UTC
Deleted Technical Notes Contents.

Old Contents:
Previously, Red Hat Enterprise Virtualization Hypervisor would not inform you when you input an ill-formed static IPv4 address.

Red Hat Enterprise Virtualization now informs you when you input an ill-formed static IPv4 address.

Comment 9 errata-xmlrpc 2011-12-06 19:15:32 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.

http://rhn.redhat.com/errata/RHBA-2011-1783.html