Bug 1066161 - [Docs] [Admin] Documetation should specify conditions to network being not in sync
Summary: [Docs] [Admin] Documetation should specify conditions to network being not in...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Julie
QA Contact: Andrew Burden
URL:
Whiteboard:
: 1059487 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-17 21:37 UTC by Marina Kalinin
Modified: 2019-04-28 09:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 13109, Administration Guide-3.3-1 Build Date: 09-01-2014 15:36:24 Topic ID: 7358-570928 [Latest]
Last Closed: 2015-02-13 04:01:04 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marina Kalinin 2014-02-17 21:37:26 UTC
Title: Editing Host Network Interfaces and Adding Logical Networks to Hosts

Describe the issue:
Documetation should specify conditions to network being not in sync based on the explanation here:
http://wiki.ovirt.org/SetupNetworks_SyncNetworks
Exact text:
"
Network will be considered 'out of sync' on the following conditions:
-    VM Netwrok is different.
-    VLAN ID is different.
-    MTU is set on the logical network, and is different. 

When network is out of sync, it is considered as an unmanaged network, until synced. This means it cannot be edited or moved if it is out of sync, unless it is set to be synced. 
"

Why is it needed?
Just would make it more clear why the network got out of sync. Right now it is not clear at all. And what does it mean that the network is out of sync.

Note:
I am not sure this would be the perfect location in the guide to specify it, but this is the only place in documentation we mention this at all.

Comment 1 Marina Kalinin 2014-02-18 14:47:09 UTC
*** Bug 1059487 has been marked as a duplicate of this bug. ***


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