Bug 1049627
Summary: | RHEV 3.2 API changing IP on hypervisor bond sub-int reqs re-passing bond opts | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dave Sullivan <dsulliva> | |
Component: | ovirt-engine | Assignee: | Moti Asayag <masayag> | |
Status: | CLOSED ERRATA | QA Contact: | Martin Pavlik <mpavlik> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.2.0 | CC: | acathrow, iheim, lbopf, lpeer, masayag, mpavlik, myakove, nyechiel, oramraz, Rhev-m-bugs, yeylon | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | 3.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | network | |||
Fixed In Version: | av3 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, using the Red Hat Enterprise Virtualization API to change options on a NIC (network interface card) sub-interface erased and reverted to default settings any pre-configured bonding options. Now, bonding options are preserved.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1068970 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-09 15:08:21 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: | 1068970, 1078909, 1142926 |
Description
Dave Sullivan
2014-01-07 21:16:15 UTC
In order to clarify the described scenario, which is verified to exist on 3.3 as well: When a vlan 10 network is attached to bond0, it creates a new device named bond0.10. When updating the bond0.10 device (i.e. boot protocol), the bonding options is being removed from from the bond0, although it wasn't designed to be changed. The engine should not override in this case the bonding options which weren't supplied by the user in this case and maintain the previous bonding options, as currently configured on the engine db. While this bug should be fixed for 3.0 api, is there any reason why not to use setup networks api ? Is it a 3.0 cluster ? works in av3 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-2014-0506.html |