[MAGNOLIA-7943] Magnolia fails to install the Imaging workspace when offline Created: 03/Nov/20  Updated: 22/Sep/21  Resolved: 19/Nov/20

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 6.2.3, 6.2.4
Fix Version/s: 6.2.5

Type: Bug Priority: Neutral
Reporter: Monica Damborenea Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: cs-bk, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File 6.2.4 error     Zip Archive imaging.zip    
Issue Links:
Problem/Incident
Relates
relates to MAGNOLIA-7844 Implement per workspace configurability Closed
relates to MGNLIMG-220 Disable indexing for imaging workspace 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:
Sprint: Maintenance 33, Maintenance 34
Story Points: 2

 Description   

One of our customers runs magnolia in a restricted environment and has no connection to external resources. When trying to install Magnolia 6.2.3 or Magnolia 6.2.4 offline (with no internet), it fails with an error caused by the Imaging workspace not created. This was working fine on Magnolia 6.2.2.

Steps to reproduce

  1. Download a clean Magnolia 6.2.3 or 6.2.4 (I tested it with both of them)
  2. Turn your laptop's internet/wifi off
  3. Try to install Magnolia
  4. You will get an error and the installation is stopped

Expected results

You should be able to complete the installation with no error.

Actual results

Unable to install Magnolia

Development notes
Find the logs attached 6.2.4 error

The first error we see is this trying to register the workspace, but unable to do it as the workspace does not exist.

2020-11-03 09:22:04,246 INFO  info.magnolia.repository.DefaultRepositoryManager : Loading workspace imaging (logical name imaging).
2020-11-03 09:22:04,267 ERROR info.magnolia.jackrabbit.ProviderImpl             : Unable to register workspace, will continue
...
2020-11-03 09:22:04,284 ERROR info.magnolia.repository.DefaultRepositoryManager : Failed to initialize workspace imaging in repository magnolia
javax.jcr.NoSuchWorkspaceException: imaging
...
2020-11-03 09:22:08,222 ERROR info.magnolia.module.ui.ModuleManagerWebUI        : Could not perform installation: javax.jcr.NoSuchWorkspaceException: imaging
...
Caused by: javax.jcr.NoSuchWorkspaceException: imaging
...
2020-11-03 09:22:08,223 ERROR info.magnolia.module.InstallContextImpl           : [31/1261 tasks - null]> Could not perform installation: javax.jcr.NoSuchWorkspaceException: imaging
...
Caused by: javax.jcr.NoSuchWorkspaceException: imaging

Workaround to solve the error:

  1. Try to install Magnolia, you will get the error but the necessary folders are generated
  2. Stop Magnolia once you get the error
  3. Go to ../repositories/magnolia/workspaces/ and paste the folder attached imaging.zip
  4. Start Magnolia back and the error should be gone.


 Comments   
Comment by Christopher Chard [ 03/Nov/20 ]

Hello Monica,
thank you for working on this!
Just as an info: We are building Magnolia automatically in a pipeline, so any additional steps wont be easy... :X
(Yes, we can try and do the workaround locally, but we'll have to see if we can add the step in the pipeline)
Again, thank you for your effort!
Chris

Comment by Christopher Chard [ 09/Nov/20 ]

Hi Monica,
is there any news on this? Will this be fixed in 6.2.4?
Cheers
Chris

Comment by Monica Damborenea [ 13/Nov/20 ]

Hi Chris,

Sorry for the delay, I was aligning internally with the team.

Unfortunately, the fix is not included in the 6.2.4 release but the root cause has been found and the fix will be included in the following one, 6.2.5.

After talking with the maintenance team, we have a new workaround that may work better for you. What's needed is to make sure 
 http://jackrabbit.apache.org/dtd/repository-2.0.dtd and  http://jackrabbit.apache.org/dtd/repository-2.0-elements.dtd are directed to a local/ internal network server.
You should be able to achieve this following these two steps:

  1. Modify the /etc/hosts to allow http://jackrabbit.apache.org to be resolved locally or in a server in your internal network.
  2. Either mount a local or modify the internal server for /dtd/repository-2.0.dtd and /dtd/repository-2.0-elements.dtd

Best,
Mónica

Comment by Christopher Chard [ 01/Dec/20 ]

Thank you for fixing this in 6.2.5!

Generated at Mon Feb 12 04:28:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.