Bug 1029033 - Link status shows disconnected although the cable is plugged.
Summary: Link status shows disconnected although the cable is plugged.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Fabian Deutsch
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks: 1029263
TreeView+ depends on / blocked
 
Reported: 2013-11-11 14:15 UTC by haiyang,dong
Modified: 2016-02-10 19:40 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1029263 (view as bug list)
Environment:
Last Closed: 2014-10-17 12:25:22 UTC
oVirt Team: Node
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 21130 0 None None None Never

Description haiyang,dong 2013-11-11 14:15:30 UTC
Description of problem:
The link status of network details page detect the physical connected state of a network cable/connector.
but after clean install ovirt-node-iso-3.1.0-0.999.1209.el6.iso and select one nic into network details page, check that
Link status shows disconnected although the cable is plugged.


Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.1209.el6.iso

How reproducible:
100%

Steps to Reproduce:

Actual results:


Expected results:
Link status shows connected when the cable is plugged.

Additional info:

Comment 1 Fabian Deutsch 2013-11-11 15:42:58 UTC
Hey,

do you know what the root cause is? The ip cmd lacking functionality or driver problems, ...?

Comment 2 haiyang,dong 2013-11-12 02:36:28 UTC
(In reply to Fabian Deutsch from comment #1)
> Hey,
> 
> do you know what the root cause is? The ip cmd lacking functionality or
> driver problems, ...?

This is due to it miss to execute "ip link set dev {dev} up" before check "1" in
/sys/class/net/{dev}/carrier.

Comment 3 Sandro Bonazzola 2014-03-04 09:22:28 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 4 Sandro Bonazzola 2014-05-08 13:56:30 UTC
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 5 Sandro Bonazzola 2014-10-17 12:25:22 UTC
oVirt 3.5 has been released and should include the fix for this issue.


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