Bug 1035676

Summary: Master setting is forgotten when LMI_BridgeSlaveSettingData is modified
Product: Red Hat Enterprise Linux 7 Reporter: Radek Novacek <rnovacek>
Component: openlmi-networkingAssignee: Radek Novacek <rnovacek>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: ovasik, rhack, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openlmi-networking-0.2.1-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:27:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Radek Novacek 2013-11-28 09:48:34 UTC
When ModifyInstance is called on LMI_BridgeSlaveSettingData, master setting configuration gets lost and therefore the slave connection can't be activated.

Comment 1 Radek Novacek 2013-11-28 09:49:51 UTC
Patch is available upstream.

Comment 3 Radek Novacek 2013-12-02 12:42:10 UTC
Fixed in openlmi-networking-0.2.1-3.el7.

Comment 5 Vladimir Benes 2014-04-16 22:03:40 UTC
after 

slave = [x for x in c.root.cimv2.LMI_IPAssignmentSettingData.instances() if x.Caption == "bridge slave"][0]
slave.Caption = "brslave"
slave.push()')
    
I can still connect to master bridge

Comment 6 Ludek Smid 2014-06-13 12:27:24 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.