Description of problem: When trying to update network filter parameter on a live update through the rest api (running VM), then the DB is getting updated (presented in the UI), but in fact the libvirt XML on the host does not get updated. Note: It's worth to mention that it is reproducible only through rest api. In case making a live update through the UI, then the libvirt XML on the host is getting updated well. Version-Release number of selected component (if applicable): ovirt-engine-4.4.5.8-0.1.el8ev.noarch How reproducible: always Steps to Reproduce: 1. create network filter parameter on VM vNIC. 2. start the VM. 3. try to update the network filter value through the rest API using the following request: PUT <engine_fqdn>/vms/<vm_id>/nics/<nic_id>/networkfilterparameters/<network_filter_id> body request: <network_filter_parameter> <name><any_filter_name></name> <value>any_filter_value</value> </network_filter_parameter> Actual results: the ovirt engine returns 200 OK and a valid body response and the UI is getting updated indeed, but the libvirt XML on the host is not. Expected results: the UI is getting updated and libvirt XML on the host gets updated too.
Workaround is to use UI until RESTAPI part is fixed
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
verified POST {fqdn}/ovirt-engine/api/vms/{vm_id}/nics/{nic_id}/networkfilterparameters works as expected verified PUT {fqdn}/ovirt-engine/api/vms/{vm_id}/nics/{nic_id}/networkfilterparameters/{network_filter_id} works as expected verified DELETE {fqdn}/ovirt-engine/api/vms/{vm_id}/nics/{nic_id}/networkfilterparameters/{network_filter_id} works as expected engine version ovirt-engine-4.4.6.3-0.8.el8ev.noarch
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.