Project

General

Profile

Bug #4601

New LSID not propagating to provenance

Added by ben leinfelder over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
provenance
Target version:
Start date:
12/03/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4601

Description

This came up as a reporting bug, but that's a symptom if something larger. I'm not sure exactly where the system breaks down, but it looks like provenance isn't staying in synch with the current LSID. At least when you open a KAR from another computer in your own Kepler installation and then make a modification to it (this assigns a brand new LSID to the workflow).
When the workflow is executed after the change (and new LSID) the provenance DB still shows the execution as the old original workflow LSID.

Can you (dan) and aaron help narrow down where this is happening?


Related issues

Blocked by Kepler - Bug #4599: changing Expression and running problematic workflow generates blank reportResolved12/03/2009

History

#1 Updated by Daniel Crawl over 9 years ago

Fixed.

#2 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4601

Also available in: Atom PDF