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.
Bug 2053520 - Incompatibilities between 8.5 virsh and libvirtd from virt:av [None8.4.0.z]
Summary: Incompatibilities between 8.5 virsh and libvirtd from virt:av [None8.4.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libvirt
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On: 2029380
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-11 13:19 UTC by RHEL Program Management Team
Modified: 2022-03-07 15:04 UTC (History)
15 users (show)

Fixed In Version: libvirt-6.0.0-35.2.el8
Doc Type: Bug Fix
Doc Text:
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
Clone Of: 2029380
Environment:
Last Closed: 2022-03-07 15:04:24 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112026 0 None None None 2022-02-11 13:24:20 UTC
Red Hat Product Errata RHSA-2022:0759 0 None None None 2022-03-07 15:04:35 UTC

Comment 2 yalzhang@redhat.com 2022-02-17 03:49:45 UTC
Reproduce the bug on libvirt-6.0.0-35.1.module+el8.4.0+11273+64eb94ef.x86_64

# cat split_daemon.sh 
#!/bin/bash
systemctl stop libvirtd.service
systemctl stop libvirtd{,-ro,-admin,-tcp,-tls}.socket
systemctl start virtqemud
for drv in qemu interface network nodedev nwfilter secret storage proxy; 
do
systemctl start virt${drv}d{,-ro,-admin}.socket ; 
done

# ./split_daemon.sh
Warning: Stopping libvirtd.service, but it can still be activated by:
  libvirtd-ro.socket
  libvirtd.socket
  libvirtd-admin.socket

# virsh -c qemu:///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 libvirt to libvirt-6.0.0-35.2.module+el8.4.0+14226+d39fa4ab.x86_64, and test again, the result is as expected.
# virsh -c qemu:///system  net-update default add  dns-txt '<txt name="example" value="example value"/>'
Updated network default live state

# virsh -c qemu:///system  net-dumpxml default 
<network>
  <name>default</name>
  <uuid>03a68dea-3acc-4dea-831e-15de6ac3329d</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='virbr0' stp='on' delay='0'/>
  <mac address='52:54:00:8a:bf:51'/>
  <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>

# virsh -c qemu:///system  net-update default delete  dns-txt '<txt name="example" value="example value"/>'
Updated network default live state

# virsh -c network:///system  net-update default add ip-dhcp-host  '<host mac="7e:75:1a:57:b9:55" name="libvirt" ip="192.168.122.100"></host>'
Updated network default live state

# virsh -c qemu:///system net-dumpxml default 
<network>
  <name>default</name>
  <uuid>03a68dea-3acc-4dea-831e-15de6ac3329d</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='virbr0' stp='on' delay='0'/>
  <mac address='52:54:00:8a:bf:51'/>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254'/>
      <host mac='7e:75:1a:57:b9:55' name='libvirt' ip='192.168.122.100'/>
    </dhcp>
  </ip>
</network>

Comment 7 yalzhang@redhat.com 2022-02-25 03:09:42 UTC
Verified according to comment 2.

Comment 11 errata-xmlrpc 2022-03-07 15:04:24 UTC
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 (Moderate: virt:rhel and virt-devel:rhel security and 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/RHSA-2022:0759


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