Bug 1030687 - spacewalk-clone-by-date with -g option produces traceback
Summary: spacewalk-clone-by-date with -g option produces traceback
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Usability
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat560-triage
TreeView+ depends on / blocked
 
Reported: 2013-11-14 23:18 UTC by DzungDo
Modified: 2017-04-28 17:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:53:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
clone-by-date.log (2.93 KB, text/plain)
2013-11-14 23:18 UTC, DzungDo 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.