Bug 1893780 - [REST] failed to delete a VNIC from a template
Summary: [REST] failed to delete a VNIC from a template
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.4.3.9
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: ovirt-4.4.3-1
: ---
Assignee: Ori Liel
QA Contact: Guy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-02 15:35 UTC by Guy
Modified: 2020-11-11 06:42 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.4.3.10-0.1
Clone Of:
Environment:
Last Closed: 2020-11-11 06:42:21 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
aoconnor: blocker-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1875412 0 medium CLOSED Request to create a nic on template gets wrong response content 2021-03-18 16:51:10 UTC

Internal Links: 1875412

Comment 2 RHEL Program Management 2020-11-03 07:36:11 UTC 
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.
Comment 4 Dominik Holler 2020-11-04 16:10:18 UTC 
fresh install ovirt-engine-4.4.3.10-0.1.el8ev.noarch: not affected

fresh install  ovirt-engine-4.4.3.7-0.22.el8ev.noarch: not affected
upgrading to ovirt-engine-4.4.3.8-0.1.el8ev.noarch and manually restarting ovirt-eneinge: not affected
upgrading to ovirt-engine-4.4.3.9-0.1.el8ev.noarch and manually restarting ovirt-eneinge: not affected
rebooting ovirt-engine-4.4.3.9-0.1.el8ev.noarch: affected
upgrading to ovirt-engine-4.4.3.10-0.1.el8ev.noarch: not affected
Comment 5 Guy 2020-11-09 08:04:01 UTC 
Verified In Version: ovirt-engine-4.4.3.10-0.1
Comment 6 Sandro Bonazzola 2020-11-11 06:42:21 UTC 
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.
Note You need to log in before you can comment on or make changes to this bug.