func icon indicating copy to clipboard operation
func copied to clipboard

Func python not working (with buildpack)

Open matzew opened this issue 5 months ago • 2 comments

With the func create -l python fn (and yes func run for localhost works just fine)

I am getting the following issue:

stern fn-000              
+ fn-00001-deployment-74d78dbb7b-vsgbr › queue-proxy
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy {"severity":"INFO","timestamp":"2025-07-01T08:26:34.744495724Z","logger":"queueproxy","caller":"sharedmain/main.go:271","message":"Starting queue-proxy","commit":"6a27004","knative.dev/key":"default/fn-00001","knative.dev/pod":"fn-00001-deployment-74d78dbb7b-vsgbr"}
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy {"severity":"INFO","timestamp":"2025-07-01T08:26:34.744536392Z","logger":"queueproxy","caller":"sharedmain/main.go:277","message":"Starting http server main:8012","commit":"6a27004","knative.dev/key":"default/fn-00001","knative.dev/pod":"fn-00001-deployment-74d78dbb7b-vsgbr"}
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy {"severity":"INFO","timestamp":"2025-07-01T08:26:34.744565025Z","logger":"queueproxy","caller":"sharedmain/main.go:277","message":"Starting http server admin:8022","commit":"6a27004","knative.dev/key":"default/fn-00001","knative.dev/pod":"fn-00001-deployment-74d78dbb7b-vsgbr"}
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy {"severity":"INFO","timestamp":"2025-07-01T08:26:34.744572572Z","logger":"queueproxy","caller":"sharedmain/main.go:277","message":"Starting http server metrics:9090","commit":"6a27004","knative.dev/key":"default/fn-00001","knative.dev/pod":"fn-00001-deployment-74d78dbb7b-vsgbr"}
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy aggressive probe error (failed 201 times): Get "http://127.0.0.1:8080/health/readiness": dial tcp 127.0.0.1:8080: connect: connection refused
fn-00001-deployment-74d78dbb7b-vsgbr queue-proxy context deadline exceeded

but the "functions deployment" stay is CrashLoopBackOff / Completed

(Note: I am running w/ func locally bulit from main)

matzew avatar Jul 01 '25 08:07 matzew

The issue seems to be on pack default builder.

Doin func deploy --builder=host --build and forcing a rebuild, for the (undocumented) host builder I get the func to deploy

matzew avatar Jul 01 '25 08:07 matzew

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

github-actions[bot] avatar Sep 30 '25 01:09 github-actions[bot]