<pre>Cannot POST /invoicing/createStripeInvoices</pre>

[ferrymul7]

Hi Team, i got the below error when issueing a curl command to test the deployment with stripe integration. Please advise what is missing. Thanks, Ferry

ferrymul@909c4acf1983 cron-job % kubectl --namespace=default run curl --image=curlimages/curl -i --tty -- sh
If you don't see a command prompt, try pressing enter.
~ $ curl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' \

--header 'Content-Type: application/json'
--data-raw '{
"month": "11",
"year": "2024"
}'

<title>Error</title>

Cannot POST /invoicing/createStripeInvoices

~ $

[jmsrpp]

Hi @ferrymul7 - we will need the pod logs from your deployed application to troubleshoot this. Please attach them here.

[ferrymul7]

@jmsrpp , i got 2 pods.

1/ curl pod give this log:
~ $ �[6n ~ $ �[J ~ $ �[Jcurl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month":"11", "year":"2024" }'

<title>Error</title>

Cannot POST /invoicing/createStripeInvoices

2/ the other btp-invoicing-srv-7c48d874f7-4fr59 pod, doesn't have any logs generated.

Please advise.

[jmsrpp]

hey @ferrymul7 - problem here then. It suggests that the route/url isn't correct for your env. At a minimum, you should see a log for btp-invoicing indicating the the CAP application is up and running, broadcasting the URL, etc.

You can delete the pod and have it recreated. Then check the log file for:

[cds] - model loaded from 1 file(s):
�[2m
srv/csn.json
�[0m
[cds] - serving InvoicingService { path: '/invoicing', impl: 'srv/invoicing-service.js' }
[cds] - server listening on { url: 'http://localhost:8080' }
[cds] - launched at 11/18/2024, 3:52:18 PM, in: 20.551s

Then double check that you are running in the default namespace. Lastly, try removing the .default from the end of your CURL URL:

curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices'

[ferrymul7]

hi @jmsrpp , I deleted the pod and recreating them in trial using command "npm run build-deploy:kyma --image_name=ferrymul/btp-invoicing --namespace=trial" with success build and deploy

btp-invoicing@1.0.0 deploy:kyma
cross-var helm upgrade --install btp-invoicing ./chart --namespace=$npm_config_namespace

Release "btp-invoicing" does not exist. Installing it now.
NAME: btp-invoicing
LAST DEPLOYED: Tue Nov 19 10:20:01 2024
NAMESPACE: trial
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing btp-invoicing version 1.0.0.

The release "btp-invoicing" is installed in namespace "trial".

Your services are available at:

• https://btp-invoicing-srv-trial.

---

Now i see the following problems in the pod events. The pod status is "ContainerCreating"

Successfully assigned trial/btp-invoicing-srv-7c48d874f7-xlfz7 to ip-10-250-1-13.ec2.internal
MountVolume.SetUp failed for volume "auth-secret" : secret "btp-invoicing-srv-auth" not found
MountVolume.SetUp failed for volume "destinations-secret" : secret "btp-invoicing-srv-destinations" not found

weirdly, after a few hours, the only left warning is :
MountVolume.SetUp failed for volume "auth-secret" : secret "btp-invoicing-srv-auth" not found

Not sure why the 2nd warning disappears though.

Please advise.

[jmsrpp]

The secrets should be mounted from the helm chart. Please double check that the helm matches what we have in the repo, aside from the version changes we implemented earlier in this issue.

[ferrymul7]

@jmsrpp , i re-clone the stripe branch and re-run all the fixes to make the build phase successful, but still have the same problem. Can you help to point out which files within helm chart that need to be fixed ? Thank you.

1. reclone the stripe branch
2. update /btp-create-api-integrations/btp-invoicing/chart/values.yaml with my github account
3. update /btp-create-api-integrations/btp-invoicing/chart/charts/web-application/templates/pod-disruption-budget.yaml with apiVersion: policy/v1
4. update /btp-create-api-integrations/btp-invoicing/package.json with "pack": "cross-var pack build $npm_config_image_name --path gen/srv --buildpack gcr.io/paketo-buildpacks/nodejs --builder paketobuildpacks/builder-jammy-base --env BP_NODE_RUN_SCRIPTS=""",
5. then run the build as usual with "npm run build-deploy:kyma --image_name=ferrymul/btp-invoicing --namespace=trial"

Same error : MountVolume.SetUp failed for volume "auth-secret" : secret "btp-invoicing-srv-auth" not found

[jmsrpp]

Hi @ferrymul7 - sorry you're encountering all these issues.

this values.yaml has the service entries. It should result in xsuaa and destination service being created in your namespace. Please confirm.

the binding is defined here

If this still fails, you can try to recreate the helm chart using cds add helm which should pick up the bindings from the package.json

Also adding my colleague, @kay-schmitteckert in case he has any idea?

[ferrymul7]

@jmsrpp , i realized now that the secrets are always deployed in default namespace. I tried with trial namespace, it always fails as above.

Anyway, i have now successfully deployed to default namespace, and below are the POD logs

******* btp-invoicing-srv-7c48d874f7-lw7q5 pod

{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:08.949Z","msg":"loaded model from 1 file(s):\n","type":"log"}
srv/csn.json
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:15.188Z","msg":"using auth strategy {\n kind: 'xsuaa',\n impl: '../layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/auth/jwt-auth'\n} \n","type":"log"}
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:19.786Z","msg":"serving InvoicingService { impl: 'srv/invoicing-service.js', path: '/odata/v4/invoicing' }","type":"log"}
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:19.788Z","msg":"server listening on { url: 'http://localhost:8080' }","type":"log"}
[cds] - launched at 11/24/2024, 10:55:05 PM, version: 7.9.5, in: 14.044s

******* curl pod
~ $ �[6n ~ $ �[J ~ $ �[Jcurl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "1
1", "year": "2024" }'

<title>Error</title>

Cannot POST /invoicing/createStripeInvoices()

I tried with the followings, but no luck:
curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'localhost:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://btp-invoicing-srv.:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://localhost:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'

Please advise.

[kay-schmitteckert]

I tried with the followings, but no luck: curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'

Hi @ferrymul7, could you test this again without the parantheses since its an action:

curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'

[ferrymul7]

@kay-schmitteckert , Tried that and it still the same error. The problem here is that there is no log, and the error messages is unhelpful to point out what is the problem.

~ $ curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year"
: "2024" }'

<title>Error</title>

Cannot POST /invoicing/createStripeInvoices

[jmsrpp]

The error message isn’t helpful because it’s never making it to the Pod. CURL is succinctly telling us it cannot resolve the hostname you’re trying. It means you need to try some basic DNS, ping, etc. Check this stack thread for a similar problem. They do some lookups, use a verbose option when running CURL, and so on. Unable to use curl and service name from inside kubernetes podstackoverflow.comJim ***@***.*** Nov 25, 2024, at 12:20 AM, Ferry Mulyadi ***@***.***> wrote: @kay-schmitteckert , Tried that and it still the same error. The problem here is that there is no log, and the error messages is unhelpful to point out what is the problem. ~ $ curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year" : "2024" }' <title>Error</title> Cannot POST /invoicing/createStripeInvoices —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ferrymul7]

@jmsrpp , i added -v in curl, and i see the following. It seems that it can connect, however it returns HTTP 404. i saw the build & deploy was successfully executed. Is there anything missing here ?

~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month":
"11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.

• Host btp-invoicing-srv.default:8080 was resolved.
• IPv6: (none)
• IPv4: 10.111.68.119
• Trying 10.111.68.119:8080...
• Connected to btp-invoicing-srv.default (10.111.68.119) port 8080
• using HTTP/1.x

POST /invoicing/createStripeInvoices() HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

• upload completely sent off: 33 bytes
  < HTTP/1.1 404 Not Found
  < X-Powered-By: Express
  < Content-Security-Policy: default-src 'none'
  < X-Content-Type-Options: nosniff
  < Content-Type: text/html; charset=utf-8
  < Content-Length: 172
  < Date: Mon, 25 Nov 2024 18:22:16 GMT
  < Connection: keep-alive
  < Keep-Alive: timeout=5
  <

<title>Error</title>

Cannot POST /invoicing/createStripeInvoices()

* Connection #0 to host btp-invoicing-srv.default left intact

[jmsrpp]

It’s an action (not a function) so please remove the () from the URL and try again. Jim ***@***.*** Nov 25, 2024, at 11:27 AM, Ferry Mulyadi ***@***.***> wrote: @jmsrpp , i added -v in curl, and i see the following. It seems that it can connect, however it returns HTTP 404. i saw the build & deploy was successfully executed. Is there anything missing here ? ~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }' Note: Unnecessary use of -X or --request, POST is already inferred. Host btp-invoicing-srv.default:8080 was resolved. IPv6: (none) IPv4: 10.111.68.119 Trying 10.111.68.119:8080... Connected to btp-invoicing-srv.default (10.111.68.119) port 8080 using HTTP/1.x POST /invoicing/createStripeInvoices() HTTP/1.1 Host: btp-invoicing-srv.default:8080 User-Agent: curl/8.11.0 Accept: / Content-Type: application/json Content-Length: 33 upload completely sent off: 33 bytes < HTTP/1.1 404 Not Found < X-Powered-By: Express < Content-Security-Policy: default-src 'none' < X-Content-Type-Options: nosniff < Content-Type: text/html; charset=utf-8 < Content-Length: 172 < Date: Mon, 25 Nov 2024 18:22:16 GMT < Connection: keep-alive < Keep-Alive: timeout=5 < <title>Error</title> Cannot POST /invoicing/createStripeInvoices() * Connection #0 to host btp-invoicing-srv.default left intact —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>