-
Notifications
You must be signed in to change notification settings - Fork 233
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
Key not found: 'info' - controller will not start #235
Comments
If you are using the Helm-based deployment, this should have been fixed by #234 (merged earlier this week). We didn't fix the older, non-Helm deployment because we're close to removing it. |
Ah, ok. I was using the non-Helm deployment but will try with Helm. |
Works with helm deployment. |
I have a openwhisk install on kubernetes since a month and everything was working fine. No issues. |
my guess is you picked up a newer controller image from dockerhub when you restarted the controller. Even if you got past this, your installation would be in trouble because the new controller isn't compatible with the old invoker pods. If you want to keep your current installation, you will need to use a tag to pull a controller image that is of the same "vintage" as the invoker image you are running. |
@dgrove-oss - I am new Open Whisk, when I am running on Windows Machine with command - $ ./gradlew core:standalone:bootRun then playground is geting open on 3232 port but api is not getting host on port 3233. API is not being running. Playground Output console below error is coming Error contacting service, status = undefined I am also getting this error - Exception in thread "main" pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.etcd.EtcdConfig. Failures are: |
@dgrove-oss same etcd error bothering me since a week |
@piyush-mishra and @Prithvi-Velicheti -- I don't think its the same problem (this is an issue from 5 years ago). I do think the problem is probably that the standalone configuration doesn't support the "new" scheduler that of a month or so is the default scheduler for OpenWhisk. The documentation/readme maybe out of date. I see in the nightly tests for standalone, we disable the new scheduler. Most likely this needs to be reflected in the documentation (for example the main README). @style95 -- does this make sense to you? You are the expert on configuring the new scheduler |
I am sorry. $./gradlew core:standalone:bootRun Exception in thread "main" pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.etcd.EtcdConfig. Failures are:
<============-> 97% EXECUTING [3m 21s]
|
@dgrove-oss |
Hi guys i have the same issue here. Do you may have a hint on how to disable the new scheduler ? I dont run it container but on my machine. I run the below. java -Dwhisk.standalone.host.name=192.168.122.69 -Dwhisk.standalone.host.internal=127.0.0.1 -Dwhisk.standalone.host.external=192.168.122.69 -jar ./bin/openwhisk-standalone.jar --couchdb --kafka --api-gw --kafka-ui |
A small update on the above. The below simple bash script did it!
|
Having issues after with new deployment... controller will not start.
Here are the container logs:
I'm new to OpenWhisk, so if there's any additional information I can provide, please let me know.
The text was updated successfully, but these errors were encountered: