Bug 1685166
Summary: | Record permanent mac address when device is enslaved in a team, or else /etc/mac-addresses will record broken information | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Pavel Cahyna <pcahyna> | |
Component: | rear | Assignee: | Pavel Cahyna <pcahyna> | |
Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> | |
Severity: | medium | Docs Contact: | Marie Hornickova <mdolezel> | |
Priority: | urgent | |||
Version: | 7.6 | CC: | djez, fkrska, jkucera, lkuprova, pasik, pcahyna, rmetrich, thozza | |
Target Milestone: | rc | Keywords: | Regression, ZStream | |
Target Release: | 7.7 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
.Teaming in the rescue system works correctly again
Updates provided by the advisory RHBA-2019:0498 fixed several problems in ReaR, affecting complex network configurations. However, in case of teaming, this update introduced another problem. If the team had multiple member interfaces, the team device was not configured correctly in the rescue system. As a consequence, after applying an update provided by RHBA-2019:0498, a work around was needed to preserve the previous behavior. This update fixes the bug in ReaR, and teaming in the rescue system now works correctly.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1685178 1690518 (view as bug list) | Environment: | ||
Last Closed: | 2019-08-06 13:12:09 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1685178, 1690518, 1691304 |
Description
Pavel Cahyna
2019-03-04 14:17:24 UTC
Upstream PR merged 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. https://access.redhat.com/errata/RHBA-2019:2273 |