[MAGNOLIA-2059] Can't delete an existing node Created: 13/Feb/08  Updated: 22/Oct/10  Resolved: 22/Oct/10

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.5.4
Fix Version/s: None

Type: Task Priority: Major
Reporter: Po Ki Chui Assignee: Jan Haderka
Resolution: Cannot Reproduce Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Redhat Linux


Attachments: PNG File Picture 1.png     Microsoft Word stacktrace.doc    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

I tried to delete a website node on a public instance, and it gave me the following popup error:

Can't delete /mynode: unable to update item:
45650e36-9cef-4160-bdcd-d6127414fbd0

Other nodes are working properly, but only this one is not deleting. The scenario is:

mynode was in the middle of activation. However, both author and public instances were not responding while the public took more than 10 minutes to clear the cache (i.e. the cache option is true on the public instance). I killed both processes because both processes got stuck when I stopped them with magnolia_control.sh. After restart, the node couldn't be activated (with attached pic). When I tried to delete the node in the public instance, it gave me the above error.



 Comments   
Comment by Ruben Reusser [ 13/Feb/08 ]

this error can be reproduced by deleting the version repository of the public site and it seems to whenever there is a problem with an activation that is not rolled back correctly.

Comment by Magnolia International [ 13/Feb/08 ]

Unless you provide a complete scenario to reproduce this error, this can't be qualified as critical bug.
If you have a support contract with us, please use the assigned support channel.
As a side note, please attach your stacktraces in attachment instead of pasting them in the description of the report. (this is editable)
Thanks.

Comment by Magnolia International [ 13/Feb/08 ]

Thanks Ruben, our message crossed each other. Why would anyone delete the version repository? It's not .. something common to do. As for an activation problem... that could very well be. Again, a reproduction scenario would help.

Comment by Philipp Bracher [ 18/Feb/08 ]

Attention: do not delete the version workspace as the nodes do have references to this nodes! This leads to inconsistencies.

Comment by Jan Haderka [ 22/Oct/10 ]

As Philipp pointed out the version workspace should not be deleted by the user. Without this the issue can't be reproduced.

Generated at Mon Feb 12 03:33:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.