[GitHub] dgrove-oss commented on issue #253: No whisk-system Namespace after installation

2018-09-04 Thread GitBox
dgrove-oss commented on issue #253: No whisk-system Namespace after installation
URL: 
https://github.com/apache/incubator-openwhisk-deploy-kube/issues/253#issuecomment-418455477
 
 
   Closing as stale; please reopen and provide answers to my questions from 
July 13 if this is still an ongoing issue for you.  


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] dgrove-oss commented on issue #253: No whisk-system Namespace after installation

2018-07-13 Thread GitBox
dgrove-oss commented on issue #253: No whisk-system Namespace after installation
URL: 
https://github.com/apache/incubator-openwhisk-deploy-kube/issues/253#issuecomment-404941602
 
 
   Thinking about how to narrow the problem.  A couple of things to look at.
   1. Did the installCatalog job succeed? It should have been doing similar 
CRUD operations using `wsk` cli and the same values for apihost.
   2. The error message suggests that `wsk` wasn't able to talk to the 
controller.  Probably worth verifying that by looking at the controller logs 
and making sure there wasn't some internal error that was interpreted by the 
`wsk` cli as a failure to connect.
   3.  Can you use `wsk` from outside the cluster and create/invoke actions?  
(Trying to see if the problem is general ingress configuration, or something 
specific to the installRouteMgmt job).
   


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] dgrove-oss commented on issue #253: No whisk-system Namespace after installation

2018-07-12 Thread GitBox
dgrove-oss commented on issue #253: No whisk-system Namespace after installation
URL: 
https://github.com/apache/incubator-openwhisk-deploy-kube/issues/253#issuecomment-404533474
 
 
   hi.  sorry I didn't get to this yesterday.  The logs in the apigateway pod 
are "normal".
   
   If the install routemgmt job completed successfully, then the system 
namespace should be there (although you can't see it using the default guest 
authorization; you have to use the system one).
   
   Try the two commands below and see if you get similar output.
   
   ```
   daves-mbp-3:incubator-openwhisk-deploy-kube dgrove$ wski --auth `kubectl -n 
openwhisk get secret whisk.auth -o jsonpath='{.data.guest}' | base64 --decode` 
namespace list
   namespaces
   guest
   daves-mbp-3:incubator-openwhisk-deploy-kube dgrove$ wski --auth `kubectl -n 
openwhisk get secret whisk.auth -o jsonpath='{.data.system}' | base64 --decode` 
namespace list
   namespaces
   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