Deployment to Cf is failing on ubuntu:jammy

[nidibm]

After changing our base image to work on FROM ubuntu:jammy as bionic is now out of support and due to security constraints , we are getting hit with deployment failures on CF.

Jun 15 17:05:40 cloudfoundry loopback-connector-provider-ibmmq ERR [WARN  tini (13)] Tini is not running as PID 1 and isn't registered as a child subreaper.
Jun 15 17:05:40 cloudfoundry loopback-connector-provider-ibmmq ERR Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
Jun 15 17:05:40 cloudfoundry loopback-connector-provider-ibmmq ERR To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm info using npm@8.19.4
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm info using node@v16.20.0
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:whichnode Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:defaults Completed in 4ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:file:/opt/node/node-v16.20.0-linux-x64/lib/node_modules/npm/npmrc Completed in 22ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:builtin Completed in 24ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:cli Completed in 3ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:env Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:file:/opt/ibm/app/.npmrc Completed in 0ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:project Completed in 4ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:file:/home/node/.npmrc Completed in 0ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:user Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:file:/opt/node/node-v16.20.0-linux-x64/etc/npmrc Completed in 0ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:global Completed in 0ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:validate Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:credentials Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:setEnvs Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load Completed in 41ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:configload Completed in 41ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:mkdirpcache Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:mkdirplogs Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:setTitle Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing config:load:flatten Completed in 6ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:display Completed in 28ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:logFile Completed in 10ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:timers Completed in 1ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load:configScope Completed in 0ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq ERR npm timing npm:load Completed in 86ms
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq OUT > loopback-connector-provider@1.0.9 start
Jun 15 17:05:41 cloudfoundry loopback-connector-provider-ibmmq OUT > node .
Jun 15 17:05:42 cloudfoundry loopback-connector-provider-ibmmq ERR npm http fetch GET 200 https://registry.npmjs.org/npm 456ms (cache miss)
Jun 15 17:05:42 cloudfoundry loopback-connector-provider-ibmmq ERR npm http fetch GET 200 https://registry.npmjs.org/npm 522ms (cache miss)
Jun 15 17:05:46 cloudfoundry loopback-connector-provider-ibmmq ERR (node:349) [DEP0152] DeprecationWarning: Custom PerformanceEntry accessors are deprecated. Please use the detail property.
Jun 15 17:05:46 cloudfoundry loopback-connector-provider-ibmmq ERR (Use `node --trace-deprecation ...` to show where the warning was created)
Jun 15 17:06:41 cloudfoundry loopback-connector-provider-ibmmq ERR Timed out after 1m0s (30 attempts) waiting for readiness check to succeed: failed to make TCP connection to 10.247.6.198:3000: dial tcp 10.247.6.198:3000: connect: connection refused```
Any input on what could have caused this or how to resolve this issue will really help us.

[nidibm]

@ibmmqmet Can you please have a look into this issue. Deployment is failing with node 18 also.

[ibmmqmet]

I don't know why you think this is anything to do with this repository. There's nothing in that log that even mentions this package. The last line showing connection failures might be where you need to investigate.

[chughts]

waiting for readiness check to succeed: failed to make TCP connection to 10.247.6.198:3000

suggests that your express app failed to start.

The rest of the logs show some npm actions, none of which suggest an error. So I think your have a readiness check listening on port 3000, but you don't have an express app, or your express app has been given another port.

You may need to raise the level of logging from the npm commands you are issuing. eg. For npm install :

npm install --loglevel verbose

For npm start

DEBUG=* npm start