RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1289600 - no connection after notebook is docked
Summary: no connection after notebook is docked
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Rashid Khan
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-08 14:20 UTC by Iveta Wiedermann
Modified: 2016-04-07 13:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-17 08:47:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Iveta Wiedermann 2015-12-08 14:20:26 UTC
Description of problem:
After I take notebook from dock where it's connected by wire, connect to wifi and then put it back to the dock station the NetworkManager states it's connected by wire but no connection is available. This last several minutes (~10 mins) then connection is available, or after NetworkManager restart.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-27.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Take notebook from a dock
2. Connect to some wifi
3. Put notebook back to a dock station

Actual results:
No connection several minutes even though NetworkManager states it's connected

Expected results:
Should be connected right after docking

Additional info:

Comment 2 Beniamino Galvani 2015-12-10 12:47:19 UTC
Can you please paste/attach the output of:

 nmcli device show
 nmcli connection
 ip addr
 ip route

when there is the connectivity problem? And also the logs captured
after increasing NetworkManager's log level with the command (as
root):

 nmcli general logging level debug

Thanks!

Comment 6 Beniamino Galvani 2015-12-17 08:47:25 UTC
I'm closing this for the moment as the issue seems not reproducible. Please reopen if it happens again, thanks.

Comment 7 Iveta Wiedermann 2015-12-17 09:41:16 UTC
Ok, thank you, Beniamino.


Note You need to log in before you can comment on or make changes to this bug.