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 1557922 - Cannot modify vNIC profile of running VM [rhel-7.5.z]
Summary: Cannot modify vNIC profile of running VM [rhel-7.5.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On: 1546971
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-19 09:19 UTC by Oneata Mircea Teodor
Modified: 2021-01-18 14:08 UTC (History)
17 users (show)

Fixed In Version: libvirt-3.9.0-14.el7_5.4
Doc Type: Bug Fix
Doc Text:
Previously, the check for a non-unique device boot order did not properly handle updates of existing devices when a new device was attached to a guest. Consequently, updating any device with a specified boot order failed. With this update, the duplicity check detects correctly handles updates and ignores the original device, which avoids reporting false conflicts. As a result, updating a device with a boot order succeeds.
Clone Of: 1546971
Environment:
Last Closed: 2018-05-14 16:11:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:1396 0 None None None 2018-05-14 16:13:02 UTC

Description Oneata Mircea Teodor 2018-03-19 09:19:35 UTC 
This bug has been copied from bug #1546971 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 7 yalzhang@redhat.com 2018-04-23 09:15:18 UTC 
1. Update elements or attributes other than "boot order" - PASS(can update);
2. Update "boot order" of interface - PASS(not support);
3. Hotplug with "boot order" with os/boot elements(negative) - PASS(unsupported);
4. Hotplug with duplicate "boot order"(negative) - PASS(report error);
5. Hotplug with "boot order" - PASS;
6. Hotplug without 'boot order' - PASS;
7. Coldplug for 3,4,5,6 - PASS ;
8. update elements or attributes other than "boot order" when vm is inactive - PASS(can update);
9. update "boot order" of interface when vm is inactive - PASS(can update);
10. Invalid "boot order"(negative) when vm is active or inactive - PASS(report error) ;

1. # virsh dumpxml rhel | grep /interface -B9
    <interface type='network'>
      <mac address='52:54:00:0f:96:f6'/>
      <source network='default' bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <filterref filter='clean-traffic'/>
      <boot order='2'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
modify the nwfilter and add link state
# cat interface1.xml
<interface type='network'>
      <mac address='52:54:00:0f:96:f6'/>
      <source network='default' bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <filterref filter='allow-ipv4'/>
     <link state='down'/>
      <boot order='2'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
# virsh update-device rhel interface1.xml
Device updated successfully
use dumpxml to check it is updated

2. update the interface boot order from '2' to '3'
# virsh update-device rhel interface2.xml
error: Failed to update device from interface2.xml
error: Operation not supported: cannot modify network device boot index setting

3. update interface to add the <boot order/> with the <boot dev/> defined in vm
# virsh update-device rhel interface4.xml
error: Failed to update device from interface4.xml
error: unsupported configuration: per-device boot elements cannot be used together with os/boot elements

4.  when there is a disk with <boot order='1'/>
# cat interface3.xml
<interface type='network'>
      <source network='default' bridge='virbr0'/>
      <model type='virtio'/>
      <boot order='1'/>
    </interface>
# virsh attach-device rhel interface3.xml
error: Failed to attach device from interface3.xml
error: unsupported configuration: boot order 2 is already used by another device
Comment 8 yalzhang@redhat.com 2018-04-23 09:17:40 UTC 
last comment is tested on libvirt-3.9.0-14.el7_5.4, all the results are as expected.
Comment 11 errata-xmlrpc 2018-05-14 16:11:44 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, 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-2018:1396
Note You need to log in before you can comment on or make changes to this bug.