[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-382217982 @yadavvipinsonu - have you been following these instructions? https://github.com/apache/incubator-openwhisk/blob/master/tools/ubuntu-setup/README.md there's also an openwhisk slack project you might want to consider for more interactive help with your issue. `openwhisk-team.slack.com` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-381579653 @yadavvipinsonu - when running the `openwhisk.yml` playbook, was the "included" `routemgmt` playbook also run and was it successful? if it was not successful, you can run that `routemgmt.yml` playbook all by itself on this system - assuming the cli was successfully installed, which it seems it was. from the `ansible` folder, run ``` ansible-playbook -i environments/local routemgmt.yml ``` confirm the `apimgmt` package was installed by the `routemgmt.yml` playbook. from the `ansible` folder run ``` wsk -i package list --auth `cat files/auth.whisk.system` ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-381221992 @yadavvipinsonu since you are using your local environment, your ansible commands will need the `-i environments/local` option to tell ansible that this is a local installation. that will cause the `openwhisk.yml` to pull the cli binary from the incubator-openwhisk release repo. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-381118355 @yadavvipinsonu - regarding the "Name or service not known" failure, are you able to download this .tgz from your system https://github.com/apache/incubator-openwhisk-cli/releases/download/latest/Openwhisk_CLI-latest-all.tgz ? that's the operation that failed above in the openwhisk.yml playbook. presumably this worked before when you installed openwhisk.. ? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-380566956 @yadavvipinsonu - the `wsk api` cli command depends on the `apimgmt` package which must be deployed to the backend. the failure observed is due to the cli attempting to invoke an action in the `apimgmt` package, but the action does not exist. this seems to point to the need to install that package in your environment. the ansible playbook for this deployment is called `routemgmt.yml`, and it should have been deployed as part of the `ansible-playbook -i environments/local openwhisk.yml` command you ran to setup your backend. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mdeuser commented on issue #2317: wsk api authentication issues
mdeuser commented on issue #2317: wsk api authentication issues URL: https://github.com/apache/incubator-openwhisk/issues/2317#issuecomment-380298414 yikes.. just now seeing this issue.. apologies for the very late response @akrabat . some thoughts.. - the openwhisk apigateway does not require any authentication, so i believe we won't surface this kind of error message in a totally open source environment - the `wsk bluemix login` command is an ibm cloud functions enhancement and has been deprecated in favor of the `wsk` plugin to the `bx` command. the api gw required token is handled transparently by the plugin working in conjunction with the `bx login` artifacts. consequently, the error messages should be more context friendly. as for the comment from @yadavvipinsonu, are you running against an apache openwhisk backend? if so, did you deploy the `apimgmt` package? you can obtain extra debug information by using the `-v` to see the cli's invocation of the backend rest apis to see which one failed. my guess is that the command to run one of the apimgmt actions was not present. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
