Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1422442

Summary: [Docs][Release Notes] Tracker for known issue with NetworkManager
Product: Red Hat Enterprise Virtualization Manager Reporter: Michael Burman <mburman>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED CURRENTRELEASE QA Contact: rhev-docs <rhev-docs>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.0CC: adahms, bgraveno, cshao, danken, huzhao, lbopf, lsurette, mburman, myakove, rbalakri, srevivo, ycui, ykaul, ylavi
Target Milestone: ovirt-4.1.1-1   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Due to an unstable slave order in NetworkManager, DHCP over a bond created by NetworkManager may receive a different IP address after adding it to Red Hat Virtualization (RHV), or after rebooting. The workaround is to avoid using DHCP on a NetworkManager-controlled bond. NetworkManager may also remove a DHCP-provided host name after a host is added to RHV. To avoid this, persist the host name explicitly via Cockpit or hostnamectl.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-31 01:39:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Burman 2017-02-15 11:02:18 UTC
Description of problem:
[DOCs] - Known issues with NetworkManager for release notes.

Bug 1367261 - bond's IP changes after reboot RHVH which is active-backup mode is a known issue and should be documented and be part of the release notes fro 4.1.1

Version-Release number of selected component (if applicable):
4.1.1-0.1.el7

Comment 1 Lucy Bopf 2017-03-02 01:48:32 UTC
Hi Michael,

Thanks for raising this. We'll use this bug to track the Known Issue. Can you please set the 'Doc Type' to 'Known Issue', and provide some draft text describing the issue?

Comment 2 Lucy Bopf 2017-04-03 06:01:08 UTC
The Release Notes requirement for this bug is now complete.

The text will appear in the next build of the Release Notes.

Moving to RELEASE_PENDING.