Issue Type: Bug Bug
Affects Versions: 5.4
Assignee: Unassigned
Created: 23/May/14 3:47 PM
Description:

Not sure if this is somewhat related to MGNLWORKFLOW-212, but this is marked as fixed for m2.

Anyhow, steps to reproduce:

  • Create an instance
  • Remove the keypair.properties file for example (in my case this file was missing from the beginning of the installation)
  • Publish a page
  • Claim task & Approve

Now it will say "Workflow approved", but the actual task fails in the background (with missing keypair properties: Caused by: java.lang.SecurityException: Private key store doesn't exist at xyz). However there is no system message or task coming back into the human tasks where I could try again or that tells me at least that it did not succeed, the activation process is effectively "lost" it seems.
A version was created of that page, can see it in the "compare version" dropdown.

Environment: Magnolia 5.3-m4
workflow 5.4-m2
Fix Versions: 5.4
Project: Magnolia Workflow Module
Priority: Major Major
Reporter: Natascha Desmarais
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to