[DOCU-652] Required Steps for updating Created: 09/Dec/15  Updated: 10/Dec/15  Resolved: 10/Dec/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Antti Hietala
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It would be nice if there would be a section under the release nodes where all generall steps are documentation to update from the last to the newest version. For Relase 5.4.3 it would be realy helpful to know that you need to add magnolia.repositories.jackrabbit.cluster.master property in the magnolia.properties also if you don't use clustering. Otherwise the update fails completly.



 Comments   
Comment by Antti Hietala [ 10/Dec/15 ]

Changed release notes and documentation to stress that both the cluster.config and cluster.master properties need to be defined together. Added a better example.

This ticket requested that each release notes contain update step. We will consider this improvement for next release notes.

Comment by Marvin Kerkhoff [ 10/Dec/15 ]

To make it realy clear can you change the alert text:

"Always define the cluster.onfig and cluster.master properties together as shown above, also if you have no cluster workspaces."

Comment by Antti Hietala [ 10/Dec/15 ]

I would consider that a bug. If you are not using Jackrabbit clustering then there should be no need to define either property.

Magnolia QA tested the 5.4.3 update with the default webapp. They did not need to add the properties.

Did you maybe have the magnolia.repositories.jackrabbit.cluster.config property as an unused leftover (without a value) in a magnolia.properties file?

Comment by Marvin Kerkhoff [ 10/Dec/15 ]

yes there is a cluster workspace, but i have this bootstrapping problems also with my not clustered workspaces in the same project.

Comment by Antti Hietala [ 10/Dec/15 ]

I see, there is a clustered workspace. How about this wording for the alert:

Always define the cluster.config and cluster.master properties together as shown above if any of your workspaces are clustered.

Generated at Mon Feb 12 01:11:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.