Bug 739893

Summary:	get xml of current job via client
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	command line	Assignee:	Bill Peck <bpeck>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, dcallagh, ebaak, mcsontos, rmancy, stl
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:	2011-10-06 03:05:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raymond Mancy 2011-09-20 10:55:31 UTC

Description of problem:
no way to get submittable xml of existing job via client (ala the web ui 'Clone'
link)

Version-Release number of selected component (if applicable):
0.7

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Marian Csontos 2011-09-20 11:10:48 UTC

Workaround: use bkr job-results - this is "dirty" full of state/results information (but this is how job-clone works internally.)

Comment 2 Marian Csontos 2011-09-20 11:40:58 UTC

(In reply to comment #1)
> Workaround: use bkr job-results - this is "dirty" full of state/results
> information (but this is how job-clone works internally.)

/me is wrong - job-clone will clean up the xml - there is clone argument there which does the trick.