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 bug fix 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:0361
Comment 11Vincent S. Cojot
2022-02-05 01:27:49 UTC
Seems we just broke plain RHEL8.5 too (virt:rhel, not virt:av):
https://github.com/openshift/installer/issues/5401
"@ElCoyote27 I encountered it in stock RHEL 8.5. I had to downgrade libvirt-6.0.0-37.1.module+el8.5.0+13858+39fdc467.aarch64 to 6.0.0-37.module+el8.5.0+12162+40884dd2.aarch64. So watch out for the latest 8.5 updates. CC @cfergeau"
Comment 12Vincent S. Cojot
2022-02-05 01:29:20 UTC
@mprivozn @yalzhang
Comment 13Vincent S. Cojot
2022-02-05 02:02:11 UTC
My RHEL 8.5 system was running libvirt 6.0.0-37.module+el8.5.0+12162+40884dd2
I received the 6.0.0-37.1.module+el8.5.0+13858+39fdc467 updates two days ago but I hadn't restarted libvirt (which is why OCP on libvirt was still working).
As soon as I restarted libvirt, things stopped working with ocp_libvirt_ipi.
@jdenemar ^^^
Comment 14Vincent S. Cojot
2022-02-06 01:05:31 UTC
Still broken on virt:av and now virt:rhel is broken too.
Here's 8.5 with virt:av
Feb 05 20:00:43 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:00:51 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:00:52 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:00:53 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:01:12 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:01:13 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
Feb 05 20:01:14 ravenvale libvirtd[4978]: Operation not supported: can't update 'bridge' section of network 'ocp4r-hztzv'
# rpm -q libvirt
libvirt-7.6.0-6.module+el8.5.0+13051+7ddbe958.x86_64
Comment 15Vincent S. Cojot
2022-02-06 01:07:02 UTC
Seems still broken in:
libvirt-6.0.0-37.1.module+el8.5.0+13858+39fdc467.x86_64
Comment 16Vincent S. Cojot
2022-02-06 01:08:29 UTC
Reproduce it on libvirt-libs-6.0.0-37.module+el8.5.0+12162+40884dd2.x86_64 Host A(192.168.122.200): libvirt-libs-6.0.0-37.module+el8.5.0+12162+40884dd2.x86_64 Host B(with the fix, 192.168.122.8): libvirt-libs-8.0.0-0rc1.1.module+el8.6.0+13853+e8cd34b9.x86_64 On host A, connect to host B libvirtd by: [host A]# virsh -c qemu+ssh://192.168.122.8/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' Update Host A to libvirt-libs-6.0.0-37.1.module+el8.5.0+13858+39fdc467.x86_64, and test again: [host A]# virsh -c qemu+ssh://192.168.122.8/system net-update default add dns-txt '<txt name="example" value="example value"/>' root.122.8's password: Updated network default live state [host A]# virsh -c qemu+ssh://192.168.122.8/system net-dumpxml default root.122.8's password: <network> <name>default</name> <uuid>693bb41a-25ba-4826-89dd-6cb3eaff0d37</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:0a:1d:2c'/> <dns> <txt name='example' value='example value'/> </dns> <ip address='192.168.124.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.124.2' end='192.168.124.254'/> </dhcp> </ip> </network>