zachschultz commented on issue #365: Bluemix Stage 1 errors creating triggers URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/365#issuecomment-324444913 @daisy-ycguo thank you! For some reason, now I am able to get the triggers and rules working when I push data to cloudant/message-hub, however when I run wskdeploy for the message-hub blueprint I'm still getting the extra action that looks like this: ``` Error creating trigger: { "name": "StatusCodeError", "statusCode": 500, "message": "500 - \"Error: Document update conflict.\"", "error": "Error: Document update conflict.", "options": { "method": "PUT", "url": "https://10.121.10.111/api/v1/web/whisk.system/messagingWeb/messageHubFeedWeb.http";, "rejectUnauthorized": false, "json": true, "body": { // REST OF PERSONAL DATA OMITTED (USER/PASS/etc.) "triggerName": "/zachary.schultz_ow/message-received-trigger", }, "headers": { "Content-Type": "application/json", "Accept": "text/plain", "User-Agent": "whisk" }, "simple": true, "resolveWithFullResponse": false, "transform2xxOnly": false }, "response": { "statusCode": 500, "body": "Error: Document update conflict.", "headers": { "server": "nginx/1.11.13", "date": "Wed, 23 Aug 2017 19:49:56 GMT", "content-type": "text/plain", "content-length": "32", "connection": "close", "access-control-allow-origin": "*", "access-control-allow-methods": "OPTIONS, GET, DELETE, POST, PUT, HEAD, PATCH", "access-control-allow-headers": "Authorization, Content-Type" }, "request": { "uri": { "protocol": "https:", "slashes": true, "auth": null, "host": "10.121.10.111", "port": 443, "hostname": "10.121.10.111", "hash": null, "search": null, "query": null, "pathname": "/api/v1/web/whisk.system/messagingWeb/messageHubFeedWeb.http", "path": "/api/v1/web/whisk.system/messagingWeb/messageHubFeedWeb.http", "href": "https://10.121.10.111/api/v1/web/whisk.system/messagingWeb/messageHubFeedWeb.http"; }, "method": "PUT", "headers": { "Content-Type": "application/json", "Accept": "text/plain", "User-Agent": "whisk", "content-length": 707 } } } } ``` Everything seems to work though, but I am still getting that message ---------------------------------------------------------------- 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: [email protected]
With regards, Apache Git Services
