[kepler-dev] [Bug 4601] New: New LSID not propagating to provenance

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4601

           Summary: New LSID not propagating to provenance
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: provenance
        AssignedTo: crawl at sdsc.edu
        ReportedBy: leinfelder at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
            Blocks: 4599


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?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.