Bug 1122010
Summary: | [RFE] Host Self-Health Log: network connectivity information | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.4.0 | CC: | acathrow, bazulay, danken, ecohen, gklein, iheim, lbopf, lpeer, mpavlik, myakove, nyechiel, sherold, tdosek, yeylon |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged, ZStream |
Target Release: | 3.4.2 | Flags: | nyechiel:
Triaged+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | network | ||
Fixed In Version: | vdsm-4.14.13-2.el6ev | Doc Type: | Enhancement |
Doc Text: |
When a Red Hat Enterprise Virtualization Hypervisor is disconnected from the network, resources become unavailable, virtual machines lose connectivity, and in some cases, the host is fenced and data is lost. Previously, there was no way to track when and why this happened. Now, a new log at /var/log/vdsm/connectivity.log allows administrators to track network connectivity. The log tracks the reported speed and duplex of host network interfaces, and when Vdsm's client (most commonly, Engine) has contacted Vdsm.
|
Story Points: | --- |
Clone Of: | 1111234 | Environment: | |
Last Closed: | 2014-09-04 12:59:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1111234 | ||
Bug Blocks: | 1123858 |
Comment 2
Michael Burman
2014-08-11 11:59:53 UTC
Moving back to MODIFIED as a new patch must be included. Verified on - vdsm-4.14.13-2.el6ev.x86_64 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. http://rhn.redhat.com/errata/RHBA-2014-1152.html |