Bug 711155

Summary: v7: sh: kudzu: command not found
Product: [Retired] Red Hat Hardware Certification Program Reporter: Russ Anderson <randerso>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: czhang, gbai, gbeshers, peterm, rja, rlandry, ykun, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 751069 (view as bug list) Environment:
Last Closed: 2011-11-08 15:41:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 751069    
Attachments:
Description Flags
hardware test patch removing attempt to call kudzu under RHEL 6 none

Description Russ Anderson 2011-06-06 16:59:46 UTC
Description of problem:

When running v7 the message "sh: kudzu: command not found" prints out.
Not sure the effect on v7.

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

[root@uv182-sys ~]# rpm -qa | grep v7
rh-tests-distribution-v7-common-1.3-20.noarch
v7-1.3-46.el6.noarch
rh-tests-distribution-v7-single-1.3-32.noarch

How reproducible:

100%


Steps to Reproduce:
1. Run a v7 test (ie v7 run --test=info --server 137.38.229.203)
  
Actual results:

  root@uv182-sys ~]# v7 run --test=info --server 137.38.229.203 
  loaded results /var/v7/results.xml
  Verifying V7 Server...
  Warning: The v7 server on 137.38.229.203 is reporting errors
  137.38.229.203 says: Error: /var/v7/export is not available
  Set server to 137.38.229.203 for  1 test(s)
  saved test plan to /var/v7/results.xml
  Warning: the test results may be too large to submit to the hardware catalog.
  File: /var/v7/results.xml is 28 MB
  Would you like to package the current results first? (y|n) n
  response: n
  
  Running the following tests:
  info                                                      
  
  Test Verification Passed
  Run these tests? (y|n) y
  response: y
  info                                                       
  
  
  
  running info on 
  sh: kudzu: command not found
  installing test from /usr/share/v7/tests/info into /tmp/v7-info-R4163O


Expected results:

Not expecting the v7 test to not find a command.

Additional info:

Apparently kudzu was dropped from RHEL6 but v7 still expects it.
http://www.redhat.com/archives/redhat-list/2010-December/msg00016.html

Comment 1 Greg Nichols 2011-07-15 14:33:12 UTC
Created attachment 513392 [details]
hardware test patch removing attempt to call kudzu under RHEL 6

Comment 5 Caspar Zhang 2011-10-21 13:18:11 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When running previous v7 versions, the following error message is printed:

  sh: kudzu: command not found

In v7 1.4, this information is no longer printed.

Comment 6 Caspar Zhang 2011-11-02 10:26:30 UTC
Bug 749068 reverted this patch, move back and mark "SanityOnly", let's waiting for a better solution.

Cleaning TechNote as well.

Comment 7 Caspar Zhang 2011-11-02 10:26:30 UTC
Deleted Technical Notes Contents.

Old Contents:
When running previous v7 versions, the following error message is printed:

  sh: kudzu: command not found

In v7 1.4, this information is no longer printed.

Comment 9 errata-xmlrpc 2011-11-08 15:41:51 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-2011-1436.html

Comment 10 errata-xmlrpc 2011-11-08 18:31:02 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-2011-1436.html