Bug 1030687

Summary: spacewalk-clone-by-date with -g option produces traceback
Product: Red Hat Satellite 5 Reporter: DzungDo <ddo>
Component: UsabilityAssignee: Grant Gainey <ggainey>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 560   
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: 2017-04-28 17:53:14 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: 924189    
Attachments:
Description Flags
clone-by-date.log none

Description DzungDo 2013-11-14 23:18:05 UTC
Created attachment 824180 [details]
clone-by-date.log

Description of problem:
Running the spacewalk-clone-by-date with -g option produces traceback.


Version-Release number of selected component (if applicable):
Satellite 5.6 with postgresql

How reproducible:
always

Steps to Reproduce:
1.spacewalk-clone-by-date -d <DATE> -l <CHANNEL_LABEL> <CLONED_LABEL> -y -g -u <USER> -p <PASSWORD>
2.
3.

Actual results:
While the process is running in the background, this command produced a traceback

Expected results:
maybe find away to suppress this traceback?

Additional info:
See attached clone-by-date.log

Comment 1 Grant Gainey 2017-04-28 17:53:14 UTC
Background-processing for spacewalk-clone-by-date was removed as part of the 5.7 release - see BZ#1207846 and BZ#1177654. Closing.