Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1570522 - Bond and slaves status are wrong when one of the slaves has the host connection [rhel-7.5.z]
Bond and slaves status are wrong when one of the slaves has the host connecti...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.5
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: sushil kulkarni
Desktop QE
Ioanna Gkioka
: Regression, ZStream
Depends On: 1548265
Blocks:
  Show dependency tree / graph
 
Reported: 2018-04-23 02:57 EDT by Oneata Mircea Teodor
Modified: 2018-05-14 12:13 EDT (History)
28 users (show)

See Also:
Fixed In Version: NetworkManager-1.10.2-14.el7_5
Doc Type: Bug Fix
Doc Text:
Due to a bug, NetworkManager did not correctly connect all slaves when the master connection was activated and the autoconnect-slaves option was set. This bug has been fixed, and slaves connections now are always activated if autoconnect-slaves is set.
Story Points: ---
Clone Of: 1548265
Environment:
Last Closed: 2018-05-14 12:13:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1406 None None None 2018-05-14 12:13 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-04-23 02:57:00 EDT 
This bug has been copied from bug #1548265 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 4 Vladimir Benes 2018-04-27 09:07:39 EDT 
both tests:
bridge_autoconnect_slaves_all_modified
bridge_autoconnect_slaves_all

passed on all architectures
Comment 7 errata-xmlrpc 2018-05-14 12:13:29 EDT 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.