Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2.0
-
None
Description
In Solr smoke test the solr-server service is always failed to start with following logs:
================================================
Notice: /Stage[main]/Solr::Server/Package[solr-server]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]/Solr::Server/File[/etc/default/solr]/content: content changed '
852d2cc2b65451471017f4a448200db0'
Notice: /Stage[main]/Solr::Server/Exec[solr init]/returns: Error: failed to initialize Solr
Error: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q solr.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
Error: /Stage[main]/Solr::Server/Exec[solr init]/returns: change from notrun to 0 failed: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q solr.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
Notice: /Stage[main]/Solr::Server/Exec[solr init]/returns: Error: failed to initialize Solr
.......
Notice: /Stage[main]/Solr::Server/Service[solr-server]: Dependency Exec[solr init] has failures: true
Warning: /Stage[main]/Solr::Server/Service[solr-server]: Skipping because of failed dependencies
================================================
'/usr/bin/solrctl init' returned 1 because solr is configured to run in cloud mode which requires zookeeper service. But at that point zookeeper service is not up. So solr-server is failed to start which leads to later smoke test failure.
Solution:
Add zookeeper service to solr-server's dependency list