cancel
Showing results for 
Search instead for 
Did you mean: 

CLD200 - Manual Deployment keeps erroring out

dhrubajyoti
Employee
Employee

SAP Extension Suite 

I am going through the CLD200 documentation stepwise and building the sample application. It has been working properly, until I get to the Manual Deployment chapter.

Issue#1: The cf push command from page #156 from the document keeps failing. When I run the cf push command, I get the below error:

user: risk-management $ cf push

Pushing apps risk-management-srv, risk-management-db-deployer to org 20afb725trial / space dev as dhrubajyoti.basak@sap.com...

Applying manifest file /home/user/projects/risk-management/manifest.yml...

Manifest applied

Packaging files to upload...

Uploading files...

9.24 KiB / 9.24 KiB 100.00% 1s

 

Waiting for API to complete processing files...

 

Staging app and tracing logs...

Downloading nodejs_buildpack...

Downloaded nodejs_buildpack

Cell 5ddf71ab-938b-4a0b-bfba-5933153fd5a9 creating container for instance cc92ccaf-1a67-403e-8b7a-66172f1e59ea

Cell 5ddf71ab-938b-4a0b-bfba-5933153fd5a9 successfully created container for instance cc92ccaf-1a67-403e-8b7a-66172f1e59ea

Downloading app package...

Downloaded app package (327.8K)

-----> Nodejs Buildpack version 1.7.63

-----> Installing binaries

engines.node (package.json): >=12.18

engines.npm (package.json): unspecified (use default)

**WARNING** Dangerous semver range (>) in engines.node. See: http://docs.cloudfoundry.org/buildpacks/node/node-tips.html

-----> Installing node 16.11.1

Copy [/tmp/buildpacks/b5d6a61786998958022dd900561c3bef/dependencies/b1672274bee4660a04596e3593464719/node_16.11.1_linux_x64_cflinuxfs3_beefe428.tgz]

Using default npm version: 8.0.0

-----> Installing yarn 1.22.17

Copy [/tmp/buildpacks/b5d6a61786998958022dd900561c3bef/dependencies/4984aeaaf5967be21b1e442d431a1957/yarn_1.22.17_linux_noarch_any-stack_08892f64.tgz]

Installed yarn 1.22.17

-----> 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

NODE_ENV=production

NODE_HOME=/tmp/contents3826178700/deps/0/node

NODE_MODULES_CACHE=true

NODE_VERBOSE=false

NPM_CONFIG_LOGLEVEL=error

NPM_CONFIG_PRODUCTION=true

-----> Building dependencies

Installing node modules (package.json + package-lock.json)

npm notice

npm notice New minor version of npm available! 8.0.0 -> 8.3.0

npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.3.0

npm notice Run `npm install -g npm@8.3.0` to update!

npm notice

npm ERR! code ENOTFOUND

npm ERR! syscall getaddrinfo

npm ERR! errno ENOTFOUND

npm ERR! network request to http://nginx-redirector.repo-cache.svc.cluster.local/repository/appstudio-npm-group/yallist/-/yallis... failed, reason: getaddrinfo ENOTFOUND nginx-redirector.repo-cache.svc.cluster.local

npm ERR! network This is a problem related to network connectivity.

npm ERR! network In most cases you are behind a proxy or have bad network settings.

npm ERR! network

npm ERR! network If you are behind a proxy, please make sure that the

npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in:

npm ERR! /tmp/cache/final/.npm/_logs/2022-01-12T16_47_09_948Z-debug.log

**ERROR** Unable to build dependencies: exit status 1

BuildpackCompileFailed - App staging failed in the buildpack compile phase

FAILED

 


Issue #2: I am also facing issues with the MTA build process. When I run the command “mbt build -t ./”, it also fails with the below error:

user: risk-management $ mbt build -t ./

[2022-01-12 20:00:41] INFO Cloud MTA Build Tool version 1.2.7

[2022-01-12 20:00:41] INFO generating the "Makefile_20220112200041.mta" file...

[2022-01-12 20:00:41] INFO done

[2022-01-12 20:00:41] INFO executing the "make -f Makefile_20220112200041.mta p=cf mtar= strict=true mode= t=\"./\"" command...

[2022-01-12 20:00:41] INFO validating the MTA project

[2022-01-12 20:00:41] INFO running the "before-all" build...

[2022-01-12 20:00:41] INFO executing the "npm ci" command...

npm WARN prepare removing existing node_modules/ before installation

npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.

npm ERR!

npm ERR!

npm ERR! Missing: hdb@^0.18.3

npm ERR!

 

npm ERR! A complete log of this run can be found in:

npm ERR! /home/user/.npm/_logs/2022-01-12T20_00_42_587Z-debug.log

[2022-01-12 20:00:42] ERROR the "before-all"" build failed: could not execute the "npm ci" command: exit status 1

make: *** [Makefile_20220112200041.mta:28: pre_build] Error 1

Error: could not build the MTA project: could not execute the "make -f Makefile_20220112200041.mta p=cf mtar= strict=true mode= t=\"./\"" command: exit status 2

 

Did anyone come across this issue & how did you resolve this?

Thanks.

- Dhruba

View Entire Topic
jannes_schofeld
Employee
Employee

Hi @JarmoTuominen and @Tiwari ,

please have a look at the following GitHub repository that we have created for the course: https://github.com/SAP-samples/extension-suite-learning-journey

The main branch contains the initial state of the project, with versions of dependencies defined in the package.json and package-lock.json, that should work. Apart from that, the repository contains solution branches for each of the exercises. So there are 2 things that you could try to get to a working state again:

Option 1:

  • Replace the package.json and package-lock.json in your existing project with the respective files from the repository.
  • Then run command npm ci within the root of your project.

Option 2:

  • Create a new folder  / workspace in your SAP Business Application Studio dev space (Open folder projects, within projects, create a new folder, e.g. risk-management-repo)
  • Switch into the new folder risk-management-repo and run command git clone https://github.com/SAP-samples/extension-suite-learning-journey
  • Now you can run command git checkout <branch> where you replace <branch> with any of the provided solution branches, e.g. solution/4_add_an_external_service
  • Run npm ci once
  • Use this as the base to go through the remaining exercises.

Please let me know if you need further assistance.

Best regards,

Jannes

Tiwari
Member
Dear Jannes, Now I am getting different error - Manifest applied Packaging files to upload... Uploading files... 9.24 KiB / 9.24 KiB 100.00% 1s Waiting for API to complete processing files... Staging app and tracing logs... Downloading nodejs_buildpack... Downloaded nodejs_buildpack Cell 52223b68-2a95-4e12-9fe8-6703e117c737 creating container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Cell 52223b68-2a95-4e12-9fe8-6703e117c737 successfully created container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Downloading app package... Downloading build artifacts cache... Downloaded app package (283K) Downloaded build artifacts cache (5.6M) -----> Nodejs Buildpack version 1.7.65 -----> Installing binaries engines.node (package.json): ^12.0.0 || ^14.0.0 || ^10.0.0 engines.npm (package.json): ^6.0.0 || ^8.0.0 || ^10.0.0 || ^12.0.0 || ^14.0.0 -----> Installing node 14.18.2 Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/44d6aeb57b09918607f5b2b4dc626375/node_14.18.2_linux_x64_cflinuxfs3_44c618d4.tgz] npm 6.14.15 already installed with node -----> Installing yarn 1.22.17 Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/4984aeaaf5967be21b1e442d431a1957/yarn_1.22.17_linux_noarch_any-stack_08892f64.tgz] Installed yarn 1.22.17 -----> 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 NODE_ENV=production NODE_HOME=/tmp/contents2921570715/deps/0/node NODE_MODULES_CACHE=true NODE_VERBOSE=false NPM_CONFIG_LOGLEVEL=error NPM_CONFIG_PRODUCTION=true -----> Building dependencies Installing node modules (package.json + package-lock.json) > @SAP/cds-compiler@2.13.8 postinstall /tmp/app/node_modules/@sap/cds-compiler > node lib/fix_antlr4-8_warning.js postinstall cds-compiler: Successfully fixed Antlr's circular dependency > @SAP-cloud-sdk/core@1.54.0 postinstall /tmp/app/node_modules/@sap-cloud-sdk/core > node postinstall.js ============================================ 🚀 SAP Cloud SDK Announcement The SAP Cloud SDK will release new major versions regularly starting in 2022. A beta version for version 2 is expected to be released in November 2021. We will ensure that upgrading takes less than one day of effort when using our upgrade guide. Read more in our announcement post: https://sap.github.io/cloud-sdk/docs/js/announcing-version-2 Set environment variable SAP_CLOUD_SDK_SILENT to hide this and future announcements. ============================================ added 193 packages from 243 contributors and audited 362 packages in 7.779s 41 packages are looking for funding run `npm fund` for details found 5 high severity vulnerabilities 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 (5.6M) Uploaded droplet (41.1M) Uploading complete Cell 52223b68-2a95-4e12-9fe8-6703e117c737 stopping instance 95199459-67ec-4413-acd9-80fedb17d6ab Cell 52223b68-2a95-4e12-9fe8-6703e117c737 destroying container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Waiting for app risk-management-srv to start... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... name: risk-management-srv requested state: started isolation segment: trial routes: risk-management-srv-sweet-impala-gz.cfapps.us10.hana.ondemand.com last uploaded: Tue 05 Apr 01:19:10 UTC 2022 stack: cflinuxfs3 buildpacks: isolation segment: trial name version detect output buildpack name nodejs_buildpack 1.7.65 nodejs nodejs type: web sidecars: instances: 0/1 memory usage: 256M start command: npm start state since cpu memory disk details #0 crashed 2022-04-05T01:19:58Z 0.0% 14.1M of 256M 159.8M of 1G Start unsuccessful TIP: use 'cf logs risk-management-srv --recent' for more information FAILED
(0)
jannes_schofeld
Employee

Hi @Tiwari,

as you can see from the message, you can use command cf logs risk-management-srv --recent to find further information about the issue. I assume this could be related to your SAP HANA Cloud trial instance. The trial version only runs for 24 hours until it gets stopped automatically. 

In your trial account, go to your Cloud Foundry dev space. There, you find the SAP HANA Cloud item in the navigational menu on the left:

Screenshot 2022-04-05 at 09.24.31.png

Open the Actions menu and select Open in SAP HANA Cloud Central:

Screenshot 2022-04-05 at 09.26.09.png

If your HANA instance shows status STOPPED, open the Actions menu and select Start to restart your database (the following screenshot shows a running instance, but the instructions apply anyways):

Screenshot 2022-04-05 at 09.27.59.png

When you have a running database, retry the deployment of your CAP application.

Best regards,

Jannes

(0)