Bug 1004365 - libvirt network schema isn't valid
libvirt network schema isn't valid
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Ján Tomko
Virtualization Bugs
Depends On: 1004364
  Show dependency treegraph
Reported: 2013-09-04 09:41 EDT by Pavel Hrdina
Modified: 2013-11-21 04:10 EST (History)
7 users (show)

See Also:
Fixed In Version: libvirt-0.10.2-24.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1004364
Last Closed: 2013-11-21 04:10:00 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)

  None (edit)
Description Pavel Hrdina 2013-09-04 09:41:01 EDT
+++ This bug was initially created as a clone of Bug #1004364 +++

Description of problem:
The network.rng schema isn't valid. There is missing element "nat" for "forward" element. The new features have been added by commits 905629f4 and 1716e7a6.

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

How reproducible:

Steps to Reproduce:
1. virsh net-dumpxml default > default.xml
2. virt-xml-validate default.xml network

Actual results:
Relax-NG validity error : Extra element forward in interleave
default.xml:4: element forward: Relax-NG validity error : Element network failed to validate content
default.xml fails to validate

Expected results:
default.xml validates
Comment 2 Ján Tomko 2013-09-05 08:01:02 EDT
Now fixed upstream:
commit 437b7944a81b648a15c657fef184f3bcd2427dac
Author:     Ján Tomko <jtomko@redhat.com>
AuthorDate: 2013-09-05 11:08:38 +0200
Commit:     Ján Tomko <jtomko@redhat.com>
CommitDate: 2013-09-05 13:45:49 +0200

    Add '<nat>' element to '<forward>' network schemas
    Commits 905629f4 and 1716e7a6 have added support for specifying
    an IPv4 range and a port range to be used by NAT:
    <forward mode='nat'>
        <address start='' end=''/>
        <port start='60000' end='65432'/>

git describe: v1.1.2-71-g437b794
Comment 5 chhu 2013-09-09 23:43:02 EDT
Reproduced with libvirt-0.10.2-23.el6.x86_64.

Verified with the packages:

Test steps:
1. # cat n1.xml
<network connections='1'>
  <forward mode='nat'>
      <port start='1024' end='65535'/>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:b7:53:29'/>
  <ip address='' netmask=''>
      <range start='' end='' />

2. # virt-xml-validate n1.xml network
n1.xml validates

3. # cat n2.xml
  <bridge name="virbr0"/>
  <forward mode="nat" dev="eth1">
      <address start='' end=''/>
      <port start='60000' end='65432'/>
  <ip address="" netmask="">
      <range start="" end=""/>
      <host mac="00:16:3e:77:f2:ed" name="a.example.com" ip=""/>
      <host mac="00:16:3e:3e:a2:1a" name="b.example.com" ip=""/>
  <ip family="ipv4" address="" netmask="">
  <ip family="ipv6" address="2001:db8:ac10:fe01::1" prefix="64">
  <ip family="ipv6" address="2001:db8:ac10:fd01::1" prefix="64">
  <ip family="ipv4" address="">

4. # virt-xml-validate n2.xml network
n2.xml validates

Test results:
current command works well, change the status to verified.
Comment 7 errata-xmlrpc 2013-11-21 04:10:00 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.