[MAGNOLIA-2445] Error in install/update still allows Magnolia to startup (and thus most likely fail miserably) when magnolia.update.auto is set to true Created: 23/Oct/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core, updatemechanism
Affects Version/s: 3.6.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2244 Further cleanup of ConfigLoader Closed
is related to MAGNOLIA-2743 startup: don't fail to start the syst... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The exception handling is different depending on which ModuleManagerUI is used (in ModuleManagerNullUI, everything happens in onStartup(), which is called in ConfigLoader, while in ModuleManagerWebUI, everything happens in calls to execute(), which are called by the InstallFilter)

In both cases, Magnolia should not start if the install or update was unsuccessful. We only need to figure out what to with incoming http requests, when using ModuleManagerNullUI. This is very much related to MAGNOLIA-2244 which asks for a review/cleanup/removal of the ConfigLoader.isBootstrapping(), .isConfigured() and .enterListeningMode() methods !



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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