Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1030687 - spacewalk-clone-by-date with -g option produces traceback
Summary: spacewalk-clone-by-date with -g option produces traceback
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Usability
Version: 560
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
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:
Last Closed: 2017-04-28 17:53:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
clone-by-date.log (deleted)
2013-11-14 23:18 UTC, DzungDo
no flags Details

Description DzungDo 2013-11-14 23:18:05 UTC
Created attachment 824180 [details]

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:

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

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.