You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by gi...@git.apache.org on 2017/08/17 21:02:43 UTC

[GitHub] zachschultz opened a new issue #365: Bluemix Stage 1 errors creating triggers

zachschultz opened a new issue #365: Bluemix Stage 1 errors creating triggers
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/365
 
 
   Using the two blueprints ([Cloudant](https://github.com/zachschultz/owbp-cloudant-trigger) and [MessageHub](https://github.com/zachschultz/owbp-message-hub-trigger)).
   
   From a clean OpenWhisk on Stage 1 Bluemix with no bindings or existing triggers/rules/actions I am trying to run my wskdeploy action on the [Cloudant-Swift blueprint](https://github.com/zachschultz/owbp-cloudant-trigger/blob/master/runtimes/swift/manifest.yaml)  but I am getting the following errors during trigger creation:
   
   The offending request:
   ```
   REQUEST:
   [POST]	https://10.121.10.111:443/api/v1/namespaces/_/actions/openwhisk-cloudant/changes?blocking=true&result=false
   Req Headers
   {
   "Authorization": [
   <MY AUTH>
   ],
   "Content-Type": [
   "application/json"
   ]
   }
   Req Body
   {{"authKey":"7e070f34-51b8-4c33-8253-8aeed88c595d:GVic78A1GAJDd5Ig7a2NkPqx7aSRTEi0O6ip008CDbg1nrMDj389oI21yMUhtkMx","dbname":"wskdeploy_test","lifecycleEvent":"CREATE","triggerName":"/_/data-inserted-trigger"}
   }
   ```
   
   The response:
   ```
   RESPONSE:Got response with code 502
   Resp Headers
   {
   "Access-Control-Allow-Headers": [
   "Authorization, Content-Type"
   ],
   "Access-Control-Allow-Origin": [
   "*"
   ],
   "Connection": [
   "keep-alive"
   ],
   "Content-Length": [
   "708"
   ],
   "Content-Type": [
   "application/json; charset=UTF-8"
   ],
   "Date": [
   "Thu, 17 Aug 2017 20:54:50 GMT"
   ],
   "Server": [
   "nginx/1.11.13"
   ]
   }
   Response body size is 708 bytes
   Response body received:
   {
   "duration": 1005,
   "name": "changes",
   "subject": "zachary.schultz@ibm.com",
   "activationId": "cd19f4665b1e4672a788a8c6405b6648",
   "publish": false,
   "annotations": [{
   "key": "limits",
   "value": {
   "timeout": 90000,
   "memory": 256,
   "logs": 10
   }
   }, {
   "key": "path",
   "value": "whisk.system/cloudant/changes"
   }],
   "version": "0.0.120",
   "response": {
   "result": {
   "error": {
   "error": "error creating cloudant trigger.",
   "message": "Document update conflict."
   }
   },
   "success": false,
   "status": "application error"
   },
   ```
   
   I also see an action after that failed, which shows this:
   
   ```
   {
       "error": {
           "error": "error creating cloudant trigger.",
           "message": "Document update conflict."
       }
   }
   Logs:
   cloudant: Error invoking whisk action: 409 { error: 'error creating cloudant trigger.',
   message: 'Document update conflict.' }
   ```
   On subsequent attempts to run `wskdeploy`, now on the "unclean" OpenWhisk, I see this in my wskdeploy output:
   
   ```
   stderr from wskDeploy:
   2017/08/17 20:59:18 Deploying package cloudant-trigger ...
   2017/08/17 20:59:18 Done!
   2017/08/17 20:59:18 Deploying package bindingopenwhisk-cloudant ...
   2017/08/17 20:59:18 Done!
   2017/08/17 20:59:18 Deploying action cloudant-trigger/process-change ...
   2017/08/17 20:59:18 Done!
   2017/08/17 20:59:18 Deploying action cloudant-trigger/process-change-cloudant-sequence ...
   2017/08/17 20:59:18 Done!
   2017/08/17 20:59:18 Deploying trigger feed data-inserted-trigger ...
   2017/08/17 20:59:18 Got error creating trigger with error message: resource already exists (code 1349070) and error code: 153.
   ```
   
   So it appears as thought the trigger couldn't be successfully created, but a non-working one is created in its place. 
   
   Running all of the above on normal production Bluemix/OpenWhisk results in no errors.
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services