Type: Regression Bug
Affects Version/s: 7.0.X, Master
If portal is running in a cluster, then configurations will be deleted if felix.fileinstall.filename does not match the osg/configs location on every node.
Steps to Reproduce
1. Set up two Liferay cluster nodes. The two nodes should be on separate machines (having one of the nodes on a VM is fine. The nodes must have different file paths for liferay.home
2. Verify that the nodes cluster properly, then bring both down
3. Put in ES config file in both nodes' /osgi/configs folder
4. Start up node 1
5. Go to Control Panel -> System Settings -> Foundation -> ElasticSearch. Verify that the ES settings match what you put in your ES config file.
6. Start up node 2 while node 1 is still running
7. You'll notice messages like these in your logs:
8. Go to Control Panel -> System Settings -> Foundation -> ElasticSearch. Node2 will not have the ES configurations listed nor will the ES configurations be apparent in Node2's log
9. Reboot Node2, the ES configurations will be applied and viewable in the log and the Foundation -> Elasticsearch above.
Expected Result: The elasticsearch configs should be set for both node 1 and node 2 and viewable in the Control Panel -> System Settings -> Foundations -> Elasticsearch page. The config should be applied on node 2's boot as well.
Actual Result: Node 2 does not appear to have the correct settings applied nor does it behave as though the config was applied.