Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 664599

Summary:	Task info is not updated
Product:	[Retired] Beaker	Reporter:	Takahiro MUNEDA <tmuneda>
Component:	web UI	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.6	CC:	bpeck, dcallagh, ebaak, lwang, mcsontos, rmancy, yanwang
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-27 03:34:23 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 Takahiro MUNEDA 2010-12-20 22:23:55 UTC

Description of problem:
When I update a task by bkr command, the info of the task is not updated. 
The rpm package itself is updated, but the info which is shown on Beaker 
Web-UI is not.

The command I used was as follows:

  % bkr task-add example.rpm

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

How reproducible:
Always

Steps to Reproduce:
1. Register a task(rpm file)
2. Modify a task(rpm file)
3. Register a task again by bkr command

Actual results:
A task info does not update.

Expected results:
A task info will be updated.

Additional info:
The task which I tried to update was 4577.

  https://beaker.engineering.redhat.com/tasks/4577

The task was originally registered by RH engineer in QE-team, and I 
tried to update. I found the problem by checking 'Updated Date.'

Comment 1 Marian Csontos 2010-12-20 22:31:41 UTC

The metadata are updated only when package is tagged. IIUC this is "Not a bug" but a "Feature".

Comment 2 Bill Peck 2010-12-20 23:27:13 UTC

Leave this bug open since you should get an error back saying you are trying to upload the same version.

Comment 3 Takahiro MUNEDA 2010-12-21 17:07:47 UTC

Ah, OK. I could understand how it should work.

Comment 4 Dan Callaghan 2011-10-27 03:34:23 UTC


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