Bug 1570521
| Summary: | Vlan over bond device cannot be shown after installation finished [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | NetworkManager | Assignee: | sushil kulkarni <sukulkar> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | urgent | Docs Contact: | Ioanna Gkioka <igkioka> |
| Priority: | high | ||
| Version: | 7.5 | CC: | atragler, bgalvani, cshao, dfediuck, fgiudici, huzhao, igkioka, jiaczhan, lrintel, mtessun, qiyuan, rbarry, rkhan, rvykydal, sbonazzo, sbueno, sukulkar, thaller, toneata, vbenes, weiwang, yaniwang, ycui, ylavi, yturgema, yzhao |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.10.2-14.el7_5 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, NetworkManager failed to automatically activate child connections when the parent device was not managed by NetworkManager yet. As a result, VLAN or other connection type were not correctly activated at boot time. This bug has
been fixed, and child connections now are activated as soon as the parent connection becomes available.
|
Story Points: | --- |
| Clone Of: | 1553595 | Environment: | |
| Last Closed: | 2018-05-14 16:13:29 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: | 1553595 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-23 06:55:44 UTC
test passed vlan_on_bond_autoconnect on all architectures 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-2018:1406 |