| Summary: | No format limit when input irregular static IPv4 address | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | cshao <cshao> |
| Component: | ovirt-node | Assignee: | Joey Boggs <jboggs> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | 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: | |
|
Description
cshao
2011-05-30 07:31:04 UTC
Change Version-Release to rhev-hypervisor-6.1-20110510.1 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.
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.
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. 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 |