Bug 681584

Summary: make bkradd should fail if trying to upload the same version of the task already present
Product: [Retired] Beaker Reporter: Karel Volný <kvolny>
Component: command lineAssignee: Bill Peck <bpeck>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.7CC: azelinka, bpeck, dcallagh, mcsontos, rmancy, stl, tmuneda
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-04-29 07:13:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Karel Volný 2011-03-02 16:28:33 UTC 
Description of problem:
If you want to resubmit a task to beaker using "make bkradd", you have to run "make tag" at first, otherwise the task does not get updated in beaker.

Version-Release number of selected component (if applicable):
rhts-test-env-4.30-1.fc14.noarch

How reproducible:
always

Steps to Reproduce:
1. cd to the testcase dir
2. open the corresponding task info page in beaker, note "Updated Date"
3. update the testcase somehow
4. make bkradd
5. refresh the task info page
  
Actual results:
the task is not replaced with the new version, the "Update Date" stays the same

Expected results:
new task version replaces the old one in beaker, "Update Date" changes to the time of submitting the new version

Additional info:
it is quite annoying to find the test didn't get updated despite the fact that submitting it (via "make bkradd") did not report any error ...
Comment 1 Bill Peck 2011-03-23 18:01:53 UTC 
We can have mutliple schedulers and we wouldn't want the tag to be incremented every time.

I think we should fix the code to return a proper error when you try and submit the same version.
Comment 3 Dan Callaghan 2011-10-27 03:34:23 UTC 
*** Bug 664599 has been marked as a duplicate of this bug. ***