Bug 1001817

Summary: sos version => sos-1.7-9.27.el5 should be added to the spec file.
Product: [Retired] Red Hat Hardware Certification Program Reporter: Rob Landry <rlandry>
Component: Test Suite (distribution)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.5.10CC: bbrock, qcai, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-08 23:53:30 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: 1001813    

Description Rob Landry 2013-08-27 20:16:42 UTC 
Description of problem:

Older versions of sos do not include the batch option.  Adding this dependency to the test suite will bring up this issue on 5.0,5.1, and 5.2 certification at the start instead of during testing.  Such that the sos errata can be installed.


Additional info:

The exception of installing the sos errata is already approved for 5.0, 5.1, and 5.2 certifications.  Details are discussed in BZ#997680.
Comment 4 Greg Nichols 2013-09-11 13:39:33 UTC 
Some additional notes on the problem, and solution.

Older versions of sos do not support the --batch option, which hwcert-client needs to gather hardware information in the info test.  

The solution is for the hwcert-client package to require newer versions of sos (sos-1.7-9.27.el5 and later) which provide the --batch option.  That way, when users install hwcert-client it will indicate that the later versions must be installed.
Comment 6 errata-xmlrpc 2013-10-08 23:53:30 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-2013-1413.html