Red Hat Bugzilla – Bug 911414
RFE: provide a way through the Config TUI to get diagnostic information
Last modified: 2014-01-21 14:26:24 EST
+++ 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
Added a diagnostic page with multipath -ll, fdisk -l, and parted -l upstream. Waiting for merge. http://gerrit.ovirt.org/#/c/12339/
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.
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.
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.
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