Bug 838300 (sync_network)

Summary: [engine][setupNetworks] Add sync network functionality
Product: Red Hat Enterprise Virtualization Manager Reporter: Mike Kolesnik <mkolesni>
Component: ovirt-engineAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED ERRATA QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: aburden, dyasny, iheim, lpeer, mavital, Rhev-m-bugs, sgordon, sgrinber, thildred, yeylon, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.ovirt.org/wiki/SetupNetworks_SyncNetworks
Whiteboard: network
Fixed In Version: si14 Doc Type: Enhancement
Doc Text:
Previously, a host that had moved between data centers could have un-synchronized logical networks; the MTU, VLAN, and VM Network properties of a logical network could be defined differently in the new data center and the host. The host would require manual intervention to synchronize its logical network definitions with the data center's. Now, you can see if a host's logical network definitions are out of sync with its data center logical network definitions, and synchronize them if desired using the "Setup Networks" action.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 19:16:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 820504, 838333    

Description Mike Kolesnik 2012-07-08 10:53:05 UTC
Description of problem:
Need to implement functionality that is described in: http://www.ovirt.org/wiki/SetupNetworks_SyncNetworks


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike Kolesnik 2012-08-05 08:50:32 UTC
http://gerrit.ovirt.org/#/c/6654/

Comment 6 errata-xmlrpc 2012-12-04 19:16:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1506.html