Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1267795 - FEAT: provide more access to client logging from the server
Summary: FEAT: provide more access to client logging from the server
Keywords:
Status: NEW
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: rhcert qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-01 04:45 UTC by Brian Brock
Modified: 2018-03-22 20:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Brian Brock 2015-10-01 04:45:28 UTC 
When launching a non-interactive test with the global debug flag set, debug output appears in a box on the cert page, above the SUT's section.  This box does not have a scrollbar, so there's not much output to see.

redhat-certification-2.0-20150930.el7.noarch
redhat-certification-hardware-1.7.1-20150901.el7.noarch

reliably reproducible

Steps to Reproduce:
1. Create a certification, with an SUT
2. Turn on the global debug output
3. launch a non-interactive test

Actual results:
output scrolls off the top of the screen, lost forever.

Expected results:
A scrollbar to make debugging info available to the user.
Comment 1 Greg Nichols 2015-10-01 12:35:22 UTC 
This display is essentially a "tail" of the last 15 lines of the client's daemon log.  There's nothing more to scroll - the intent is to provide some status feedback of the client under test, rather than extensive log review.

Let's move this bug to a feature request for more extensive client log access, most likely via some specific UI for the purpose.
Note You need to log in before you can comment on or make changes to this bug.