Bug 1035676 - Master setting is forgotten when LMI_BridgeSlaveSettingData is modified
Summary: Master setting is forgotten when LMI_BridgeSlaveSettingData is modified
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openlmi-networking
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 09:48 UTC by Radek Novacek
Modified: 2016-12-01 00:32 UTC (History)
3 users (show)

Fixed In Version: openlmi-networking-0.2.1-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:27:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.