-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standalone Openwhisk error: Key not found 'etcd' #5475
Comments
The standalone mode is not supported with the new scheduler that became a default scheduler. https://github.com/apache/openwhisk/blob/master/ansible/group_vars/all#L501 |
I have edited https://github.com/apache/openwhisk/blob/master/ansible/group_vars/all#L501 to default to false, but the problem still persists. Are there any follow-up steps before the standalone should work? |
I had the same issue. @style95 I don't think the standalone mode uses the Ansible config. The config file for standalone is core/standalone/build/resources/main/standalone.conf, but after I modified it, the problem still exists. |
I run into the same problem when trying to deploy with Kubernetes in Docker. When I try to deploy a local build to some of the pods, they keep crashing and will not initialize. Here is an example using the controller component:
However, when I deploy openWhisk through: I want to use OpenWhisk for my research project, but this is making it hard to start developing. |
@paulzhn @pprabh2007 @Tarik-Kada This is because of the updated spi configurations. I would ponder over how to handle this part. whisk.spi {
ArtifactStoreProvider = org.apache.openwhisk.core.database.CouchDbStoreProvider
ActivationStoreProvider = org.apache.openwhisk.core.database.ArtifactActivationStoreProvider
MessagingProvider = org.apache.openwhisk.connector.kafka.KafkaMessagingProvider
ContainerFactoryProvider = org.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider
LogStoreProvider = org.apache.openwhisk.core.containerpool.logging.DockerToActivationLogStoreProvider
LoadBalancerProvider = "org.apache.openwhisk.core.loadBalancer.LeanBalancer"
EntitlementSpiProvider = org.apache.openwhisk.core.entitlement.LocalEntitlementProvider
AuthenticationDirectiveProvider = org.apache.openwhisk.core.controller.BasicAuthenticationDirective
InvokerProvider = org.apache.openwhisk.core.invoker.InvokerReactive
InvokerServerProvider = org.apache.openwhisk.core.invoker.DefaultInvokerServer
DurationCheckerProvider = org.apache.openwhisk.core.scheduler.queue.NoopDurationCheckerProvider
} |
Thanks for your reply! I have tried the proposed fix, but it still does not work. I updated the SPI like you said, and this is the result of both
It still doesn't boot properly, as you can see. Is there anything I need to do in between editing the code and trying to build/run? In the end, I hope to be able to use openWhisk to develop on, whether this would be using the standalone version or a version that runs in Kubernetes in Docker doesn't matter. |
I believe this is not related to the standalone mode as you can't even compile the code because of not-found errors. You may want to try |
I have been stuggling for the last two days to try and get a working environment up and running. Using the devtools quick-start to spin up an environment using Docker Compose. First issue I encountered was the Kafka container failing:
This appears to be resolved by using the latest image (wurstmeister/kafka:latest). Other containers start and stay running. The only exceptions are the Controller and Invoker containers. They are both failing with: 'Exception in thread "main" pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.etcd.EtcdConfig. Failures are:
We are currently evaluating OpenWhisk and it has been quite challenging so far with the current documentation. Could you please point me in the direction as to how I might adjust the SPI's for this deployment configuration? Thanks! |
@matt-8319 |
Thanks @style95. Do you know if it is possible to use the admin tools with standalone mode? |
@matt-8319 |
Getting this as well when trying to up a standalone.
|
Environment details:
Ubuntu: 22.04
Steps to reproduce the issue:
Provide the expected results and outputs:
Additional information you deem important:
None, consistently get the same error
The text was updated successfully, but these errors were encountered: