Bug 440687

Summary: hts info test failing
Product: [Retired] Red Hat Hardware Certification Program Reporter: IBM Bug Proxy <bugproxy>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-04 17:05:11 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:
Attachments:
Description Flags
sysreport
none
hts plan file
none
info ouput.log file
none
md5sum file for sysreport none

Description IBM Bug Proxy 2008-04-04 14:24:38 UTC 
=Comment: #0=================================================
William J. Goodrich <billgo.com> - 2008-04-04 09:42 EDT
Problem description:
The info test failed with hts5.2-8. 

Running ./info.py:
OS Version RHEL4, kernel rpm kernel-2.6.9-67.EL
HTS version 5.2, release 8
+ rpm -ql kernel-2.6.9-67.EL
Checking Kernel: PASS
Verification of HTS rpm failed
Error: "rpm -V --nomtime --nomode --nocontexts hts" returned 1
...finished running ./info.py, exit code=1
Comment 1 IBM Bug Proxy 2008-04-04 14:24:43 UTC 
Created attachment 300435 [details]
sysreport
Comment 2 IBM Bug Proxy 2008-04-04 14:24:46 UTC 
Created attachment 300436 [details]
hts plan file
Comment 3 IBM Bug Proxy 2008-04-04 14:24:47 UTC 
Created attachment 300437 [details]
info ouput.log file
Comment 4 IBM Bug Proxy 2008-04-04 14:24:49 UTC 
Created attachment 300438 [details]
md5sum file for sysreport
Comment 5 Greg Nichols 2008-04-04 17:05:11 UTC 
This failure is due to the fact that your HTS rpm (5.2 release 8) came from my
development system rather than a legitimate build.   This is not a bug.
Comment 6 IBM Bug Proxy 2008-04-04 19:32:54 UTC 
------- Comment From billgo.com 2008-04-04 15:27 EDT-------
Closing as not a bug.