*** The wcm.io Project is closing down this JIRA Instance in favor of GitHub issues. *** Please use the corresponding GitHub projects to report issues - or the mailing list for general discussion.

Issues

Select view

Select search mode

 
31 of 31

Symlink for default.farm and default.vhost must not be generated when using custom farm

Fixed

Description

According to the comments in the default dispatcher farm and default vhost config, when you create a customized copy of the default one, the symlink to the default file must be removed from enabled_farms and enabled_vhosts

Currently the role still sets the symlinks despite of having customized copies

https://github.com/wcm-io-devops/conga-aem-definitions/blob/develop/conga-aem-definitions/src/main/roles/aem-dispatcher-cloud.yaml#L267-L270

This causes the following warning in disaptcher log

Also only one of these farms gets loaded randomly which also causes problems like 404 when the default farm is loaded instead of project specific one

Details

Assignee

Reporter

Components

Priority

Created October 18, 2021 at 10:27 AM
Updated October 26, 2021 at 11:54 AM
Resolved October 26, 2021 at 11:54 AM

Activity

Show:

Stefan SeifertOctober 26, 2021 at 11:54 AM

thanks, PR is merged

Masoud RozatiOctober 22, 2021 at 10:53 AM

I adjusted the ticket title because we should also remove the default.vhost symlink.
If those two symlinks are removed the error is solved. We just tested it.

Nico BellackOctober 18, 2021 at 2:45 PM

Also only one of these farms gets loaded randomly which also causes problems like 404 when the default farm is loaded instead of project specific one

This also happens for me. vanity_urls are deactivated by default in the default_farm file. Activating it in the project-specific file isn’t recognized since the default file gets loaded instead.

Masoud RozatiOctober 18, 2021 at 10:41 AM

Pull request for the solution:

Loading...