Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1557922 - Cannot modify vNIC profile of running VM [rhel-7.5.z]
Cannot modify vNIC profile of running VM [rhel-7.5.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
7.5
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Jiri Denemark
yalzhang@redhat.com
: Regression, ZStream
Depends On: 1546971
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-19 05:19 EDT by Oneata Mircea Teodor
Modified: 2018-05-14 12:13 EDT (History)
17 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1546971
Environment:
Last Closed: 2018-05-14 12:11:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:1396 None None None 2018-05-14 12:13 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-03-19 05:19:35 EDT
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 05:15:18 EDT
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 05:17:40 EDT
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 12:11:44 EDT
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.