Simple CAP Application Deploy BTP (Trial) : Found no compatible cell

[WouterLemaire]

Hi Experts,

I was having issues deploying my CAP application (complex) to BTP, running into a deploy issue:

Error staging application "xxx": NoCompatibleCell - Found no compatible cell

So I started from scratch with a simple application: 

- Install a fresh Trial Account

- Create a HANA DB (mapping to CF dev space)

- Create a simple CAP application in BAS, single table, simple service to display table entries

- Add hana (for production), Add mta

- Create MTA file

- Deploy to CF

All vanilla steps, explained in many blogs and CAPIRE. Nothing special, no manipulation of any package.json or any other files. 

However, no matter what I do. I always run into a CF deploy issue in the staging step stating (dmol extract) :

Failed to stage build: found no compatible cell with placement tag "trial" (STDERR, API)

I can't find any valuable information on this error, other than some non SAP related blogs mentioning that the stacks are not available on CF. As I did a clean install on a Trial account I assume the BTP environment is installed correctly. 

Would be great if somebody could provide some hints as I'm not able to deploy any application to BTP.

Regards,

Tom 

[WouterLemaire]

Can you share the mta.yaml file? I’m guessing that you are using somewhere trial as a plan for a service that doesn’t have trial as a plan. Besides that, can you als check the logs of the service while deploying? (Only if it is already available)

[tom_grillo]

Hi Wouter,

Thanks for getting back to me.

Here is the extract of my mta.yaml file:

_schema-version: 3.3.0

ID: bpm

version: 1.0.0

description: "A simple CAP project."

parameters:

enable-parallel-deployments: true

build-parameters:

before-all:

- builder: custom

commands:

- npm ci

- npx cds build --production

modules:

- name: bpm-srv

type: nodejs

path: gen/srv

parameters:

buildpack: nodejs_buildpack

readiness-health-check-type: http

readiness-health-check-http-endpoint: /health

build-parameters:

builder: npm

provides:

- name: srv-api # required by consumers of CAP services (e.g. approuter)

properties:

srv-url: ${default-url}

requires:

- name: bpm-auth

- name: bpm-db

- name: bpm

type: approuter.nodejs

path: app/router

parameters:

keep-existing-routes: true

disk-quota: 256M

memory: 256M

requires:

- name: srv-api

group: destinations

properties:

name: srv-api # must be used in xs-app.json as well

url: ~{srv-url}

forwardAuthToken: true

- name: bpm-auth

- name: bpm-db-deployer

type: hdb

path: gen/db

parameters:

buildpack: nodejs_buildpack

requires:

- name: bpm-db

resources:

- name: bpm-auth

type: org.cloudfoundry.managed-service

parameters:

service: xsuaa

service-plan: application

path: ./xs-security.json

config:

xsappname: bpm-${org}-${space}

tenant-mode: dedicated

- name: bpm-db

type: com.sap.xs.hdi-container

parameters:

service: hana

service-plan: hdi-shared

Steps executed:

- Created a fresh BTP account

- Create a HANA Cloud service

- Open BAS

- cds init bpm --add tiny-sample

- cds add hana,xsuaa,approuter --for production

- cds add mta

- npm i

- mbt build -t gen --mtar mta.tar

- cf deploy gen/mta.tar

that's it, vanilla example however stuck during deploy. Extract dmol:

2024-11-23T23:59:10.97+0000 [API/6] OUT Uploading app package for app with guid 6a44f818-a9aa-44cd-940f-e971e551a499
2024-11-23T23:59:20.76+0000 [API/23] OUT Scaling process: "web"
2024-11-23T23:59:20.98+0000 [API/0] OUT Creating build for app with guid 6a44f818-a9aa-44cd-940f-e971e551a499
2024-11-24T00:00:38.62+0000 [API/7] ERR Failed to stage build: found no compatible cell with placement tag "trial"
2024-11-24T00:00:43.16+0000 [API/21] OUT Creating build for app with guid 6a44f818-a9aa-44cd-940f-e971e551a499
2024-11-24T00:02:09.47+0000 [API/19] ERR Failed to stage build: found no compatible cell with placement tag "trial"

Regards,

Tom

[gregorw]

I can confirm the issue:

  2024-11-24T10:29:26.33+0100 [API/20] ERR Failed to stage build: found no compatible cell with placement tag "trial"

when I try to deploy https://github.com/SAP-samples/cap-sflight. It's a freshly created Trial acocunt in the Extension Landscape us10-002 (https://api.cf.us10-002.hana.ondemand.com). Seems someone forgot to do the needed setup for trial in this CF landscape.

The CF Coding is: https://github.com/cloudfoundry/auction/blob/main/auctiontypes/types.go#L27

Maybe @thomas_jung can trigger the right people?

[tom_grillo]

Thanks Gregorw! Will fwd. this to Thomas Jung. At least I can stop refreshing/ installing BTP accounts now, knowing it's a general issue with the BTP installation.

[tom_grillo]

Hi, thanks for the update. I can confirm it's working now. However when disabling/ enabling CF in my subaccount, the org name change xxx_ext and I was not able to list the orgs (CLI: cf orgs) anymore (no orgs available). I ended up reinstalling my BTP trial account, now it's working again.

[Ofra · Accepted solution]

Hi

There was a configuration issue on trial US10, in order to fix the issue please disable the CF runtime and enable it again.

In Case the issue is not resolved, i recommend to create a new sub account.

Ofra

[EunSeok_Bang · Accepted solution]

I confirm the zone is now back to 001 when enabling CF.

[tom_grillo · Accepted solution]

Hi, thanks for the update. I can confirm it's working now. However when disabling/ enabling CF in my subaccount, the org name change xxx_ext and I was not able to list the orgs (CLI: cf orgs) anymore (no orgs available). I ended up reinstalling my BTP trial account, now it's working again.