This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2169245 - update interface with passt backend by update-device report successfully, but no changes
Summary: update interface with passt backend by update-device report successfully, but...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-13 02:37 UTC by yalzhang@redhat.com
Modified: 2023-09-22 16:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 16:14:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7338 0 None Migrated None 2023-09-22 16:14:23 UTC
Red Hat Issue Tracker RHELPLAN-148376 0 None None None 2023-02-13 02:38:05 UTC

Description yalzhang@redhat.com 2023-02-13 02:37:30 UTC 
Description of problem:
update interface with passt backend by update-device report successfully, but no changes for passt related parameters

Version-Release number of selected component (if applicable):
libvirt-9.0.0-4.el9.x86_64
passt-0^20221110.g4129764-1.el9.x86_64
qemu-kvm-7.2.0-8.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start a vm with interface as below:
$ virsh dumpxml test --xpath //interface
<interface type="user">
  <mac address="52:54:00:bc:fa:5e"/>
  <source dev="eno1"/>
  <ip address="172.17.2.4" family="ipv4" prefix="24"/>
  <ip address="2001:db8:ac10:fd01::20" family="ipv6"/>
  <model type="virtio"/>
  <backend type="passt" logFile="/home/test/passt.log"/>
  <alias name="net0"/>
  <address type="pci" domain="0x0000" bus="0x08" slot="0x00" function="0x0"/>
</interface>

2. Try to update the interface by update-device to add the port forwarding setting:
$ cat interface.xml
<interface type="user">
  <mac address="52:54:00:bc:fa:5e"/>
  <source dev="eno1"/>
  <ip address="172.17.2.4" family="ipv4" prefix="24"/>
  <ip address="2001:db8:ac10:fd01::20" family="ipv6"/>
  <model type="virtio"/>
<portForward proto="tcp">
    <range start="31339" to="41339"/>
  </portForward>
  <backend type="passt" logFile="/home/test/passt.log"/>
  <alias name="net0"/>
  <address type="pci" domain="0x0000" bus="0x08" slot="0x00" function="0x0"/>
</interface>

$ virsh update-device test interface.xml
Device updated successfully

3. check the live xml, there is no changes
$ virsh dumpxml test --xpath //interface
<interface type="user">
  <mac address="52:54:00:bc:fa:5e"/>
  <source dev="eno1"/>
  <ip address="172.17.2.4" family="ipv4" prefix="24"/>
  <ip address="2001:db8:ac10:fd01::20" family="ipv6"/>
  <model type="virtio"/>
  <backend type="passt" logFile="/home/test/passt.log"/>
  <alias name="net0"/>
  <address type="pci" domain="0x0000" bus="0x08" slot="0x00" function="0x0"/>
</interface>

Actual results:
update-device report succeed, but there is no changes

Expected results:
The passt related parameters may not support update on the fly, so the live update should fail.

Additional info:
live update to update the link state for passt backend interface succeed and network work properly
Comment 1 Laine Stump 2023-02-15 20:33:16 UTC 
Actually *anything* in <backend> should prevent an update-device. I'm testing a patch now.
Comment 2 Laine Stump 2023-02-15 21:07:36 UTC 
Posted fix upstream:

https://listman.redhat.com/archives/libvir-list/2023-February/237876.html
Comment 3 Laine Stump 2023-02-21 19:45:55 UTC 
Fix pushed upstream:

commit 110d209263022c6029e398116154562518e4a474 (HEAD -> master, upstream/master)
Author: Laine Stump <laine>
Date:   Wed Feb 15 15:29:56 2023 -0500

    qemu: forbid updating any attributes of an interface <backend> with update-device
Comment 4 RHEL Program Management 2023-09-22 16:11:40 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-22 16:14:28 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.