You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I subscribed the "Sustainable SaaS" application, the status turned "Subscription Failed".
There was no log in the srv module, so I guess the subscription failed at its very early stage. Where can I check for detailed errors when a subscription to a SaaS application fails?
Additional information:
The log below is emitted when the srv module started. The is a message There is no service, therefore does not serve multitenancy!. Does this indicate that some configuration for multitenancy is missing?
Warning: `cds run` will be removed with the next major version.
Use `cds-serve` instead in your start script. Set it with:
npm pkg set scripts.start="cds-serve"
[cds] - loading server from { file: 'srv/server.js' }
[cov2ap] - [HPM] Proxy created: / -> http://localhost:8080
[cov2ap] - [HPM] Proxy rewrite rule created: "^/v2" ~> ""
[cds] - loaded model from 1 file(s):
�[2m
srv/csn.json
�[0m
[cds] - connect to db > hana {
clientsecret: '...',
sm_url: 'https://service-manager.cfapps.us10.hana.ondemand.com',
url: 'https://e0f125b2trial.authentication.us10.hana.ondemand.com',
xsappname: '2914f2e1-4f77-41ac-b3f6-0fd3d8a84984!b164206|service-manager!b1476',
clientid: 'sb-2914f2e1-4f77-41ac-b3f6-0fd3d8a84984!b164206|service-manager!b1476'
}
[cds] - IAS Binding is missing, therefore user management will not interact with any IAS instance
[cds] - serving AdminService { path: '/catalog/AdminService', impl: 'srv/admin-service.js' }
[cds] - serving PublicService { path: '/catalog/PublicService', impl: 'srv/public-service.js' }
There is no service, therefore does not serve multitenancy!
[cds] - mock launchpad listening on { flpUrl: 'http://localhost:8080/#Shell-home' }
[cds] - server listening on { url: 'http://localhost:8080' }
[cds] - launched at 6/18/2023, 8:31:42 PM, version: 6.8.1, in: 848.948ms
The text was updated successfully, but these errors were encountered:
Hi @miyasuta - sorry we somehow missed out on this issue! Please excuse the delayed response though! I assume, the missing multitenancy services, might be caused by an incorrect build process.
Did you ensure to run an npm install --include=dev and cds build --production, before building your container images? Thanks for double-checking! You should see the following logs during the build process, indicating, that the required mtxs resources for multitenancy are part of your build.
I am on the "Subscribe a Tenant Subaccount" section of the basic tutorial. I am using BTP trial environment.
https://github.com/SAP-samples/btp-kyma-cap-multitenant-susaas/tree/main/docu/2-basic/5-subscribe-consumer-subaccount
When I subscribed the "Sustainable SaaS" application, the status turned "Subscription Failed".
There was no log in the srv module, so I guess the subscription failed at its very early stage. Where can I check for detailed errors when a subscription to a SaaS application fails?
My updated code is stored in the Git repository below.
https://github.com/miyasuta/btp-kyma-cap-multitenant-susaas
Additional information:
The log below is emitted when the srv module started. The is a message
There is no service, therefore does not serve multitenancy!
. Does this indicate that some configuration for multitenancy is missing?The text was updated successfully, but these errors were encountered: