Bug 1030687 – spacewalk-clone-by-date with -g option produces traceback

Bug 1030687 - spacewalk-clone-by-date with -g option produces traceback

Summary:	spacewalk-clone-by-date with -g option produces traceback

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	Usability (Show other bugs)
Sub Component:
Version:	560
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Grant Gainey
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	sat560-triage
	Show dependency tree / graph

Reported:	2013-11-14 18:18 EST by DzungDo
Modified:	2017-04-28 13:53 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-04-28 13:53:14 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
clone-by-date.log (2.93 KB, text/plain) 2013-11-14 18:18 EST, DzungDo	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description DzungDo 2013-11-14 18:18:05 EST

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 13:53:14 EDT

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.