Bug 1177594
Summary: | virt-xml-validate cannot validate "bridge" attribute in "interface/source" element | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | yisun |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED DEFERRED | QA Contact: | chhu |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | dyuan, jsuchane, libvirt-maint, mzhan, xuzhang, yafu, yalzhang, yanqzhan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-03 17:01:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
yisun
2014-12-29 09:49:52 UTC
*** Bug 1261790 has been marked as a duplicate of this bug. *** Add one more scenario, on domain type of 'kvm', the validate command will fail as well. Version-Release number of selected component (if applicable): libvirt-1.3.2-1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.5.x86_64 steps to reproduce: 1. # virsh start R7.2 Domain R7.2 started 2. # virsh dumpxml R7.2 <domain type='kvm' id='33'> <name>R7.2</name> ...... <interface type='network'> <mac address='52:54:00:fa:12:cc'/> <source network='default' bridge='virb119'/> <target dev='vnet1'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> ..... # virsh dumpxml R7.2 > b.xml # virt-xml-validate b.xml Relax-NG validity error : Extra element devices in interleave b.xml:34: element devices: Relax-NG validity error : Element domain failed to validate content b.xml fails to validate 3. delete the "bridge='virbr119'" in b.xml # vim b.xml # virt-xml-validate b.xml b.xml validates # echo $? 0 The attribute 'macTableManager' has same issue. Add latest test results here for your reference: RHEL7.5 # rpm -q libvirt qemu-kvm-rhev libvirt-3.9.0-7.el7.x86_64 qemu-kvm-rhev-2.10.0-16.el7.x86_64 1.# cat V-bridge-macTableManager.xml|grep 'source network' <source network='default' bridge='virbr0' macTableManager='libvirt'/> # virt-xml-validate V-bridge-macTableManager.xml V-bridge-macTableManager.xml validates # echo $? 0 2.If use "virsh edit", the domain xml can be successfully saved. But the "bridge='virbr0' macTableManager='libvirt'" will disappear When check the xml again by virsh edit. RHEL7.3 libvirt-2.0.0-10.el7_3.11.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.15.x86_64 1.# cat q35-bridge.xml |grep 'source network' <source network='default' bridge='virbr0' macTableManager='libvirt'/> # virt-xml-validate q35-bridge.xml Relax-NG validity error : Extra element devices in interleave q35-bridge.xml:33: element devices: Relax-NG validity error : Element domain failed to validate content q35-bridge.xml fails to validate # cat q35-macTableManager.xml |grep 'source network' <source network='default' macTableManager='libvirt' /> # virt-xml-validate q35-macTableManager.xml Relax-NG validity error : Extra element devices in interleave q35-macTableManager.xml:33: element devices: Relax-NG validity error : Element domain failed to validate content q35-macTableManager.xml fails to validate 2.If use virsh edit, both of xml with them will fail to save: # virsh edit q35 error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Extra element devices in interleave Element domain failed to validate content Failed. Try again? [y,n,i,f,?]: Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution. |