Skip to content
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

Example fortunewhale workflow failing #141

Closed
BlakeMScurr opened this issue May 3, 2018 · 2 comments
Closed

Example fortunewhale workflow failing #141

BlakeMScurr opened this issue May 3, 2018 · 2 comments

Comments

@BlakeMScurr
Copy link

Hi all, can I get a hand with debugging the example workflow? I'm just running through the usage instructions in the readme, and I'm hitting some errors:

curl <my cluster IP>:<fission router external port>/fortunewhale
Internal server error (fission)

The logs from all my fission functions are giving errors like this:

Error from server (BadRequest): a container name must be specified for pod workflow-f62cdf48-4f15-11e8-8968-080027940780-nrtwlfqg-5b68wfdt, choose one of: [workflow fetcher]

which implies to me that there is a fetcher container in each pod that is unaccounted for.

Also, the fission router gives this error:

2018/05/03 22:29:38 Not cached, getting new service for &ObjectMeta{Name:fortunewhale,GenerateName:,Namespace:default,SelfLink:/apis/fission.io/v1/namespaces/default/functions/fortunewhale,UID:421993ae-4f19-11e8-8968-080027940780,ResourceVersion:3874,Generation:1,CreationTimestamp:2018-05-03 21:30:53 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}
2018/05/03 22:29:56 Failed to get service for function fortunewhale: Invalid argument - Failed to download url : Get : unsupported protocol scheme ""

and I'm not sure what to make of it, perhaps it's related.

Versions:

fission -version
Client Version: {"GitCommit":"0247ea488e7e2f4b23b46ec9757d7b381caccf81","BuildDate":"2018-04-02T22:54:21Z","Version":"0.7.0"}
Server Version: {"GitCommit":"0247ea488e7e2f4b23b46ec9757d7b381caccf81","BuildDate":"2018-04-02T22:54:21Z","Version":"0.7.0"}
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:10:24Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
@erwinvaneyk
Copy link
Member

Hey @BlakeMScurr :) what version of Workflows are you using?

@BlakeMScurr
Copy link
Author

I'm using 0.2.0. It's all working now though after I restarted kubernetes, reinstalled fission, and made sure the fission storagesvc pod was running, as it was pending before. Cheers :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants