Bug 990965 - Report error when configure network with static IPv4 mode
Report error when configure network with static IPv4 mode
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Fabian Deutsch
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2013-08-01 06:04 EDT by haiyang,dong
Modified: 2014-01-21 14:47 EST (History)
14 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-5.el6
Doc Type: Bug Fix
Doc Text:
--no tech note required
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 14:47:49 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-21 19:14:30 EST

  None (edit)
Description haiyang,dong 2013-08-01 06:04:22 EDT
Description of problem:
It reports "An error appeared in the UI: < InvalidData 'The field must contain a valid IPv4 address or an empty string.'>" when configure network with static IPv4 mode.

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

How reproducible:

Steps to Reproduce:
1. Install rhevh6.5.
2. Select a NIC and configure it with IPv4 Static mode.
   Bootprotocol :   ( ) Disabled   ( ) Auto     ( ) DHCP      (X) Static
   IP Address   :           Netmask :       32
   Gateway      :

Actual results:
1. After step2, it reports "An error appeared in the UI: < InvalidData 'The field must contain a valid IPv4 address or an empty string.'> ".

Expected results:
1. After step2, it can set ipv4 address with static mode successfully.

Additional info:
Comment 2 Mike Burns 2013-08-15 09:21:18 EDT
may be related to bug 990984
Comment 3 Fabian Deutsch 2013-09-11 05:34:22 EDT
Tested as follows:

1. Apply patch
2. Run in dev mode:
   PYTHONPATH=src/ scripts/ovirt-node-setup --dry --defaults /tmp/cfg_dummy
3. Configure NIC
4. Enter
   Netmask: 32
5. Error is shown, <Save> is disabled

6. Enter
<Save> is enabled and save does not raise an error.
Comment 6 haiyang,dong 2013-10-18 00:22:28 EDT
Test version:

It still reports "An error appeared in the UI: < InvalidData 'The field must contain a valid IPv4 address or an empty string.'>" when setting netmask of ipv4 settings as Prefix Length.
So need re-assigned this bug again.
Comment 10 haiyang,dong 2013-10-31 05:18:29 EDT
Test version:

Now the item of Netmask only accept "a valid IPv4 address or an empty string",
also when input a valid IPv4 address or an empty string and apply it, no exception error was thrown. 

so this bug has been fixed, change it into "VERIFIED".
Comment 13 Cheryn Tan 2013-11-07 19:34:46 EST
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 15 errata-xmlrpc 2014-01-21 14:47:49 EST
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.


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