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.
Cause:
When a libvirt API is called all its arguments are copied into a so called RPC packet which is then sent to the daemon where the arguments are extracted and the API is called.
However, in case of virNetworkUpdate() there was a bug which swapped two arguments on the client side as the RPC packet was being constructed.
Consequence:
This resulted in daemon having two arguments swapped which ten lead to spurious errors. For instance, when user wanted to add a TXT record to a network the following error was reported:
Operation not supported: can't update 'ip' section of network 'net-1'
Fix:
The fix consists of fixing the order of arguments so that the correct order is preserved.
Result:
Users can now update their networks happily.
More info can be found in the cover letter of original patches:
https://listman.redhat.com/archives/libvir-list/2021-March/msg00052.html
https://listman.redhat.com/archives/libvir-list/2021-March/msg00758.html
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 (virt:rhel and virt-devel:rhel bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1214
Reproduce on hostA with: libvirt-4.5.0-42.module+el8.2.0+6024+15a2423f.x86_64 qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 To a hostB with: libvirt-8.0.0-4.module+el8.6.0+14186+211b270d.x86_64 qemu-kvm-6.2.0-6.module+el8.6.0+14165+5e5e76ac.x86_64 Current to newer, failed: [hostA]# virsh -c qemu+ssh://hostB/system net-update default add dns-txt '<txt name="example" value="example value"/>' error: Failed to update network default error: Operation not supported: can't update 'ip' section of network 'default' Verify with: hostA: libvirt-4.5.0-42.1.module+el8.2.0+14235+7beeb3f6.x86_64 qemu-kvm-2.12.0-99.module+el8.2.0+11704+da06378b.6.x86_64 hostB. hostC: libvirt-daemon-4.5.0-42.module+el8.2.0+6024+15a2423f.x86_64 qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 [hostA]# yum module update virt:rhel # systemctl restart libvirtd 1. Latest to newer, becomes succeed. [hostA] # virsh -c qemu+ssh://hostB/system net-update default add dns-txt '<txt name="example" value="example value"/>' Updated network default live state # virsh -c qemu+ssh://hostB/system net-dumpxml default <network> <name>default</name> <uuid>ce7fe5df-1915-482b-9f93-687ae56d9256</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:bb:de:38'/> <dns> <txt name='example' value='example value'/> </dns> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254'/> </dhcp> </ip> </network> 2.Latest to older, succeed. [hostA]virsh -c qemu+ssh://hostC/system net-update default add dns-txt '<txt name="example" value="example value"/>' Updated network default live state 3.Latest to self, succeed. [hostA]# virsh -c qemu:///system net-update default add dns-txt '<txt name="example" value="example value"/>' Updated network default live state 4.Older to latest, still failed, as known. [hostC]# virsh -c qemu+ssh://hostA/system net-update default add dns-txt '<txt name="example" value="example value"/>' error: Failed to update network default error: Operation not supported: can't update 'ip' section of network 'default'