Bug 647730 - Can not clone recipesets: missing whiteboard
Summary: Can not clone recipesets: missing whiteboard
Keywords:
Status: CLOSED DUPLICATE of bug 659141
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.5
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard:
: 659305 659638 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-29 09:06 UTC by Marian Csontos
Modified: 2014-12-08 01:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-02 22:35:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Marian Csontos 2010-10-29 09:06:54 UTC
Description of problem:
Recipesets cannot be cloned due to missing whiteboard.

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

How reproducible:
100%

Steps to Reproduce:
1. try to clone any RecipeSet from command line
2.
3.
  
Actual results:
  $ bkr job-clone RS:45292
  <Fault 1: 'exceptions.AttributeError:whiteboard'>
  Submitted: []


Expected results:
  job is scheduled

Additional info:

Comment 1 Marian Csontos 2010-12-02 08:41:07 UTC
The same applies to WebUI:

Go to any job (e.g. [1] having a lot of RS) and try cloning a recipe set e.g. [2].

 [1] https://beaker.engineering.redhat.com/jobs/35582
 [2] https://beaker.engineering.redhat.com/jobs/clone?recipeset_id=60010

This results in a ISE 500.

I can still use "Clone" at Job level, but that's inconvenient when I want only a single RecipeSet.

Changing the component to Scheduler:

I believe it's Scheduler who is to blame: when returning a RecipeSet/Recipe it should also include upper level elements (i.e. job for RS and recipeSet for R) and all required components (e.g. whiteboard for job.)

Comment 2 Marian Csontos 2010-12-02 14:15:32 UTC
*** Bug 659305 has been marked as a duplicate of this bug. ***

Comment 3 Raymond Mancy 2010-12-02 22:35:36 UTC

*** This bug has been marked as a duplicate of bug 659141 ***

Comment 4 Raymond Mancy 2010-12-02 23:08:32 UTC
Btw, a quick workaround for this is to set a 'product' on your job. It should then all work fine.

Comment 5 Marian Csontos 2010-12-03 00:30:03 UTC
That's not that quick when using web UI on older jobs, as that can not be used.

And using command line, it's not easy to edit the XML.

Comment 6 Raymond Mancy 2010-12-03 00:38:17 UTC
Why not? I just did it on a job of mine from 6 months ago.

It's not a comprehensive solution, it's a workaround until the proper fix is deployed in less than a weeks time.

Comment 7 Marian Csontos 2010-12-03 07:46:05 UTC
All right. Did not notice the milestone. I can live with it.

Comment 8 Bill Peck 2010-12-03 14:04:19 UTC
*** Bug 659689 has been marked as a duplicate of this bug. ***

Comment 9 Dan Callaghan 2010-12-05 21:05:11 UTC
*** Bug 659638 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.