search

IBM / watson-assistant-slots-intro

A Chatbot for ordering a pizza that demonstrates how using the IBM Watson Assistant Slots feature, one can fill out an order, form, or profile.
https://developer.ibm.com/patterns/assemble-a-pizza-ordering-chatbot-dialog/
Apache License 2.0
146 stars 218 forks source link

cannot deploy this app by toolchain #138

Open mgoryo opened 4 years ago

mgoryo commented 4 years ago

Hi,

I am having a problem at the very first step. I cannot deploy this app by using toolchain. First, it was said that I did not have an instance of Continuous Delivery, so I made it. However, I cannot deploy it still. It was just said "start unsuccessful". The log shows authentication and creating service instances are ok.

I would appreciate if you give me some advice or help. (please tell me if I should add some more information or a part of the log.)

Thanks, Mai

ronanb3 commented 4 years ago

Hi, I have the same issue.

I created a whole new IBM Cloud account to make sure I don't have any impact from other installations.

The deploy stage is not working. There is an issue and it may come from there.

I did the local installation and it works fine. I don't have the same warnings locally.

Here is the log.

Preparing to start the job...
Pipeline image: latest
Preparing the build artifacts...
Pulling pipeline base image latest ...
cf login -a "https://api.eu-gb.cf.cloud.ibm.com" -u apikey -p "****" -o "ronan.bourlier@imerir.com" -s "dev"
API endpoint: https://api.eu-gb.cf.cloud.ibm.com
Authenticating...
OK

Targeted org ronan.bourlier@imerir.com

Targeted space dev

API endpoint:   https://api.eu-gb.cf.cloud.ibm.com (API version: 2.151.0)
User:           ronan.bourlier@imerir.com
Org:            ronan.bourlier@imerir.com
Space:          dev
Creating service instance wcsi-conversation-service in org ronan.bourlier@imerir.com / space dev as ronan.bourlier@imerir.com...
OK

Service wcsi-conversation-service already exists
Pushing from manifest to org ronan.bourlier@imerir.com / space dev as ronan.bourlier@imerir.com...
Using manifest file /home/pipeline/58660cda-ace4-419b-9290-9570c014ae70/manifest.yml
Getting app info...
Deprecation warning: Use of 'buildpack' attribute in manifest is deprecated in favor of 'buildpacks'. Please see https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#deprecated for alternatives and other app manifest deprecations. This feature will be removed in the future.

Updating app with these attributes...
  name:                watson-conversation-rboi
  path:                /home/pipeline/58660cda-ace4-419b-9290-9570c014ae70
  buildpacks:
    sdk-for-nodejs
  command:             npm start
  disk quota:          1G
  health check type:   port
  instances:           1
  memory:              256M
  stack:               cflinuxfs3
  services:
    wcsi-conversation-service
  env:
    NPM_CONFIG_PRODUCTION
  routes:
    watson-conversation-rboi.eu-gb.mybluemix.net

Updating app watson-conversation-rboi...
Mapping routes...
Comparing local files to remote cache...
Packaging files to upload...
Uploading files...

 0 B / 1.61 MiB    0.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00%
 1.61 MiB / 1.61 MiB  100.00% 1s

Waiting for API to complete processing files...

Stopping app...

Staging app and tracing logs...
   Downloading sdk-for-nodejs...
   Downloaded sdk-for-nodejs
   Cell 88e5a9ec-c812-480a-811d-0ed518220d88 creating container for instance 4266034c-91d4-429d-b332-173c0d67ae45
   Cell 88e5a9ec-c812-480a-811d-0ed518220d88 successfully created container for instance 4266034c-91d4-429d-b332-173c0d67ae45
   Downloading app package...
   Downloading build artifacts cache...
   Downloaded app package (4.5M)
   Downloaded build artifacts cache (13.9M)
   -----> IBM SDK for Node.js Buildpack v4.3-20200606-1928
          Based on Cloud Foundry Node.js Buildpack 1.7.20

   -----> Installing binaries
          engines.node (package.json): >= 10.0.x
          engines.npm (package.json): > 6.0.x
          **WARNING** Dangerous semver range (>) in engines.node. See: http://docs.cloudfoundry.org/buildpacks/node/node-tips.html
          Attempting to install: 12.18.0
   -----> Installing node 12.18.0
          Copy [/tmp/buildpacks/74557d86f560e13b996ce3626558fba3/dependencies/ab41c108d5eea630c0f445d664dfd94a/node_12.18.0_linux_x64_cflinuxfs3_8aaf25f7.tgz]
          npm 6.14.4 already installed with node
   -----> Installing yarn 1.22.4
          Copy [/tmp/buildpacks/74557d86f560e13b996ce3626558fba3/dependencies/d9f0c5147bcb9ee798f041978c157822/yarn-1.22.4-any-stack-24ca2294.tgz]
          Installed yarn 1.22.4
   -----> Creating runtime environment
          PRO TIP: It is recommended to vendor the application's Node.js dependencies
          Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring
          NPM_CONFIG_PRODUCTION=false
          NODE_ENV=production
          NODE_HOME=/tmp/contents739387763/deps/0/node
          NODE_MODULES_CACHE=true
          NODE_VERBOSE=false
          NPM_CONFIG_LOGLEVEL=error
   -----> Building dependencies
          Installing node modules (package.json + package-lock.json)
   > websocket@1.0.31 install /tmp/app/node_modules/websocket
   > (node-gyp rebuild 2> builderror.log) || (exit 0)
   make: Entering directory '/tmp/app/node_modules/websocket/build'
     CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
     SOLINK_MODULE(target) Release/obj.target/bufferutil.node
     COPY Release/bufferutil.node
     CXX(target) Release/obj.target/validation/src/validation.o
     SOLINK_MODULE(target) Release/obj.target/validation.node
     COPY Release/validation.node
   make: Leaving directory '/tmp/app/node_modules/websocket/build'
   > phantomjs-prebuilt@2.1.16 install /tmp/app/node_modules/phantomjs-prebuilt
   > node install.js
   PhantomJS not found on PATH
   Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
   Saving to /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
   Receiving...
   Received 22866K total.
   Extracting tar contents (via spawned process)
   Removing /tmp/app/node_modules/phantomjs-prebuilt/lib/phantom
   Copying extracted folder /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2-extract-1597844330926/phantomjs-2.1.1-linux-x86_64 -> /tmp/app/node_modules/phantomjs-prebuilt/lib/phantom
   Writing location.js file
   Done. Phantomjs binary available at /tmp/app/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs
   added 645 packages from 936 contributors and audited 646 packages in 35.479s
   found 42 vulnerabilities (41 low, 1 high)
     run `npm audit fix` to fix them, or `npm audit` for details
          **WARNING** Unmet dependencies don't fail npm install but may cause runtime issues
          See: https://github.com/npm/npm/issues/7494
          Contrast Security no credentials found. Will not write environment files.
   Exit status 0
   Uploading droplet, build artifacts cache...
   Uploading droplet...
   Uploading build artifacts cache...
   Uploaded build artifacts cache (13.9M)
   Uploaded droplet (67.9M)
   Uploading complete
   Cell 88e5a9ec-c812-480a-811d-0ed518220d88 stopping instance 4266034c-91d4-429d-b332-173c0d67ae45
   Cell 88e5a9ec-c812-480a-811d-0ed518220d88 destroying container for instance 4266034c-91d4-429d-b332-173c0d67ae45
   Cell 88e5a9ec-c812-480a-811d-0ed518220d88 successfully destroyed container for instance 4266034c-91d4-429d-b332-173c0d67ae45

Waiting for app to start...
FAILED
Start unsuccessful

TIP: use 'cf logs watson-conversation-rboi --recent' for more information

Finished: FAILED
rhagarty commented 4 years ago

@Ronanb3 - just pushed some changes that should get you around this issue. Please update your local repo and try again. I've updated the "Deploy to CF" readme with some more instructions.

The main issue is that the Assistant credentials generated during the deployment are not sufficient for the app. After the deployment fails (like your message above), you need to add the proper credentials to the application run-time environment and then re-start the app. The updated instructs provide more details.