hunhoffe opened a new issue, #5223: URL: https://github.com/apache/openwhisk/issues/5223
<!-- We use the issue tracker for bugs and feature requests. For general questions and discussion please use https://openwhisk.apache.org/slack.html or https://openwhisk.apache.org/community.html instead. Do NOT share passwords, credentials or other confidential information. Before creating a new issue, please check if there is one already open that fits the defect you are reporting. If you open an issue and realize later it is a duplicate of a pre-existing open issue, please close yours and add a comment to the other. Issues can be created for either defects or enhancement requests. If you are a committer than please add the labels "bug" or "feature". If you are not a committer please make clear in the comments which one it is, so that committers can add these labels later. If you are reporting a defect, please edit the issue description to include the information shown below. If you are reporting an enhancement request, please include information on what you are trying to achieve and why that enhancement would help you. For more information about reporting issues, see https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#raising-issues Use the commands below to provide key information from your environment: You do not have to include this information if this is a feature request. --> ## Environment details: * Local ansible deployment * Ubuntu 20.04, Docker 20.10.12 ## Steps to reproduce the issue: 1. Follow Ansible deployment instructions for new Scheduler 2. Modify them to deploy with couchdb backend and not Elastic Search 3. Will hit error at the following command: ```ansible-playbook -i environments/$ENVIRONMENT openwhisk.yml -e db_activation_backend=CouchDB``` ## Provide the expected results and outputs: I'd expected it to deploy correctly. ## Provide the actual results and outputs: The scheduler will fail to deploy. The error ansible gives is: ``` fatal: [scheduler0]: FAILED! => {"attempts": 12, "changed": false, "elapsed": 0, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://172.17.0.1:14001/ping"} Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused> ``` This isn't very helpful, I don't think, but the scheduler logs are more informative: ``` [2022-04-25T18:10:32.291Z] [INFO] [#tid_sid_unknown] [WatcherService] watch endpoint: WatchEndpoint(whisk/instance/scheduler0/lease,7802908987417965063,false,lease-service,Set(DeleteEvent)) Exception in thread "main" java.lang.ExceptionInInitializerError at java.base/java.lang.J9VMInternals.ensureError(J9VMInternals.java:186) at java.base/java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:175) at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:121) at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:112) at org.apache.openwhisk.core.scheduler.Scheduler.<init>(Scheduler.scala:91) at org.apache.openwhisk.core.scheduler.Scheduler$.main(Scheduler.scala:339) at org.apache.openwhisk.core.scheduler.Scheduler.main(Scheduler.scala) Caused by: pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreConfig. Failures are: at 'whisk': - Key not found: 'activation-store'. at pureconfig.package$.getResultOrThrow(package.scala:139) at pureconfig.package$.loadConfigOrThrow(package.scala:161) at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<init>(ElasticSearchActivationStore.scala:420) at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<clinit>(ElasticSearchActivationStore.scala) ... 5 more ``` It appears the scheduler is looking for ElasticSearch backend, and not CouchDB. I'm hoping to learn if the scheduler can function with CouchDB as an activation store or not. ## Additional information you deem important: * Ansible scheduler documentation says it's recommended to use ElasticSearch at the activation store but does not say it's required. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
