Bug 1255158

Summary:	el6 unhelpful failure message in audio test for hdmi
Product:	Red Hat Certification Program	Reporter:	brose
Component:	redhat-certification-hardware	Assignee:	brose
Status:	CLOSED ERRATA	QA Contact:	Brian Brock <bbrock>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	gnichols, kbenoit, rlandry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	1.6.6-20150826.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1255486 (view as bug list)		Environment:
Last Closed:	2015-09-03 13:15:52 UTC	Type:	Bug
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:
Bug Blocks:	1254659, 1255486

Description brose 2015-08-19 19:37:46 UTC

Description of problem:
The failure message in the audio test for hdmi is unhelpful.

Version-Release number of selected component (if applicable):


How reproducible:
consistent

Steps to Reproduce:
1.unplug any hdmi or DP cable from system
2.run hdmi audio test
3.

Actual results:
aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:1
Error: aplay command failed

Expected results:

Error: No HDMI/DP audio found active, please make sure the cable is connected and device turned on.

Additional info:

Leave existing error in place for internal speakers.

Comment 4 brose 2015-08-20 17:53:07 UTC

*** Bug 1255160 has been marked as a duplicate of this bug. ***

Comment 8 Ken Benoit 2015-09-01 19:17:01 UTC

Verified using redhat-certification-1.0-20150813.el6, redhat-certification-hardware-1.6.6-20150826.el6, and redhat-certification-information-1.6.6-20150826.el6. Message now states:

Error: No active HDMI/DP audio devices found
       Please make sure the cable is connected and device turned on

Marking as verified.

Comment 10 errata-xmlrpc 2015-09-03 13:15:52 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.

https://rhn.redhat.com/errata/RHBA-2015-1710.html