Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 595642 - RFE: clone: make recipe-sets clonable instead of recipes
RFE: clone: make recipe-sets clonable instead of recipes
Status: CLOSED CURRENTRELEASE
Product: Beaker
Classification: Community
Component: web UI (Show other bugs)
0.5
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: Bill Peck
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-25 05:22 EDT by Marian Csontos
Modified: 2011-06-13 14:45 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-05 13:56:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marian Csontos 2010-05-25 05:22:07 EDT
Cloning a recipe does not make much sense. It does not matter for single-host, it is not that useful for multi-host.
Comment 1 Bill Peck 2010-07-21 08:38:17 EDT
Denying beaker-blocker flag as we didn't have working cloning before.
Comment 2 Raymond Mancy 2010-08-01 20:31:07 EDT
Any harm in just adding in clonability of RecipeSet's, or is it so absurd to have cloneable recipes that there is/never will be a use case for it and it should be removed ?
Comment 3 Marian Csontos 2010-08-02 01:38:37 EDT
IMO having cloneable RecipeSets, cloning single recipe would be useless:
- for single host RecipeSet it is just the same
- for multi-host tests, cloning only one server/client without the rest does not make sense. Such a test will not run correctly...

I vote for removing.
Comment 5 Marian Csontos 2010-08-03 02:06:10 EDT
Thanks. That's quite a change!

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