Bug 1055441 - [NetworkLabels] Host nics labels are being deleted when setup networks api is called
Summary: [NetworkLabels] Host nics labels are being deleted when setup networks api is...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-api
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.4.0
Assignee: Moti Asayag
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks: 1024889
TreeView+ depends on / blocked
 
Reported: 2014-01-20 09:32 UTC by Moti Asayag
Modified: 2014-04-01 05:00 UTC (History)
6 users (show)

Fixed In Version: ovirt-3.4.0-beta2
Clone Of:
Environment:
Last Closed: 2014-03-31 12:27:35 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 23507 0 None None None Never
oVirt gerrit 23524 0 None None None Never

Description Moti Asayag 2014-01-20 09:32:17 UTC
Description of problem:
The network labels on nic level are being added via the api:
/api/hosts/{host:id}/nics/{nic:id}/labels

When a setup networks command is sent via:
/api/hosts/{host:id}/nics/setupnetworks

The former labels are being removed from the nics.

How reproducible:
always

Steps to Reproduce:
1. Label a nic (via UI or REST)
2. POST a /api/hosts/{host:id}/nics/setupnetworks 

Actual results:
All the labels are being cleared from the host's nics.

Expected results:
The labels should be preserved

Additional info:
The setup networks api doesn't use the patch mechanism to preserve any interface property that wasn't sent by the user. Instead, it creates a new interface entity and set only the provided nic attributes.
There should be a 'labels only' patch to preserve the nic labels.

Comment 1 Martin Pavlik 2014-02-17 14:58:54 UTC
works with  oVirt Engine Version: 3.4.0-0.7.beta2.el6

Comment 2 Sandro Bonazzola 2014-03-31 12:27:35 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released


Note You need to log in before you can comment on or make changes to this bug.