Bug 1315060

Summary: spacecmd package-search doesn't return results when ran from command line, same works from spacecmd shell
Product: Red Hat Satellite 5 Reporter: Ilan Green <igreen>
Component: ClientAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED ERRATA QA Contact: Jan Hutař <jhutar>
Severity: medium Docs Contact:
Priority: medium    
Version: 570CC: ggainey, igreen, jhutar, tlestach, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: spacecmd-2.3.0-5-sat Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-22 12:24:20 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: 1127217    

Description Ilan Green 2016-03-06 11:10:03 UTC 
Description of problem:
spacecmd package search doesn't return results when ran from a shell script

Version-Release number of selected component (if applicable):
spacecmd-2.3.0-4.el6sat.noarch

How reproducible:
make a shell script
#!/bin/bash
# script to search for packages within red hat satellite
#
/usr/bin/spacecmd -- package_search $1

Steps to Reproduce:
1. create script
2. run "<script>  <package name or partial name>" # Select a package which is available
3.

Actual results:
no results

Expected results:
List of packages matching the search criteria

Additional info:
Per the below link it seems a fix is available in upstream and it is all about changing one line in the spacecmd
https://github.com/spacewalkproject/spacewalk/commit/ffd53a926df0ef997eb40d2dd4eae656208a777e
Comment 1 Tomas Lestach 2016-03-07 08:57:51 UTC 
Moving to MODIFIED, since the fix is available in upstream.
Comment 19 errata-xmlrpc 2016-08-22 12:24:20 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-2016-1645.html