Bug 911414

Summary:	RFE: provide a way through the Config TUI to get diagnostic information
Product:	Red Hat Enterprise Linux 6	Reporter:	Mike Burns <mburns>
Component:	ovirt-node	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.5	CC:	acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, lnovich, mburns, ovirt-bugs, ovirt-maint, rbarry, ycui
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-node-3.0.0-6.el6	Doc Type:	Enhancement
Doc Text:	The hypervisor did not offer a way to show disk diagnostics in the user interface, and users were required to drop to a rescue shell in order to check disk status. There is now a "Diagnostics" page which allows users to check the output of: multipath -ll fdisk -l parted -s -l lsblk From within the user interface, and the output is displayed as part of normal user interaction, allowing for end-users to verify the status of Fiber Channel or iSCSI targets easily.	Story Points:	---
Clone Of:	794858	Environment:
Last Closed:	2014-01-21 19:26:24 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:	794858, 865017
Bug Blocks:

Description Mike Burns 2013-02-14 22:44:24 UTC

+++ This bug was initially created as a clone of Bug #794858 +++

Add a new tab to the Config TUI for Diagnostics, or make this a subsection of the support menu.

User should be able to enter a hostname or ip address in the TUI and get results of ping back to determine whether or not network connectivity is good

User should be able to view output of multipath -ll and fdisk -l commands (these two might be best shown as 'logs' since we can treat output from them similar to running less on a log file.

--- Additional comment from Mike Burns on 2013-02-05 09:09:25 EST ---

Separate ping test command has been implemented already.

Adding other command output is something we can evaluate for 2.7.0

Comment 1 Ryan Barry 2013-03-01 16:21:26 UTC

Added a diagnostic page with multipath -ll, fdisk -l, and parted -l upstream.  Waiting for merge.

http://gerrit.ovirt.org/#/c/12339/

Comment 8 wanghui 2013-10-11 10:09:37 UTC

Test version:
rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
ovirt-node-3.0.1-3.el6.noarch

Test steps:
1. Clean install rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
2. Check the Diagnostics page.

Test results:
1. After step2, the diagnostics page is added. 
2. The current tools are as follows and the function of them are correctly.
   multipath -ll
   fdisk -l
   parted -s -l
   lsblk

So the bug is fixed in rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso. I will recheck it when I got official build.

Comment 9 wanghui 2013-10-18 11:14:21 UTC

Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6.noarch

Test steps:
1. Clean install rhev-hypervisor6-6.5-20131017.0.iso.
2. Check the Diagnostics page.

Test results:
1. After step2, the diagnostics page is added. 
2. The current tools are as follows and the function of them are correctly.
   multipath -ll
   fdisk -l
   parted -s -l
   lsblk

The bug is fixed in rhev-hypervisor6-6.5-20131017.0.iso. So change the bug's status from ON_QA to VERIFIED.

Comment 11 Cheryn Tan 2013-11-08 00:26:30 UTC

This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 13 errata-xmlrpc 2014-01-21 19:26:24 UTC

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-0033.html