Is anyone else seeing

FlytePropeller &  user defined pod executions

logs having for the most part static timestamps? We're running EKS with FluentBit deployed that pushes logs to Cloudwatch, but seeing the following

Thanks for reporting Edgar. @icy-agent-73298 / @glamorous-carpet-83516 if you could take a look at this.

what log you got when you expand them? I guess you got this warning. If so, upgrading propeller can fix it.

{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554033","routine":"worker-2","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:01Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554039","routine":"worker-2","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:02Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554040","routine":"worker-2","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:02Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554040","routine":"worker-3","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:08Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554064","routine":"worker-3","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:08Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554064","routine":"worker-2","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:18Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554064","routine":"worker-3","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:24Z"}
{"json":{"exec_id":"abqczk9ch2lrjtb664th","node":"n0","ns":"flytesnacks-development","res_ver":"5554064","routine":"worker-3","tasktype":"python-task","wf":"flytesnacks:development:<http://example_sd.wf|example_sd.wf>"},"level":"warning","msg":"No plugin found for Handler-type [python-task], defaulting to [container]","ts":"2022-11-03T01:27:24Z"}

Yes, upgrading to which version? Currently its set to cr.flyte.org/flyteorg/flytepropeller-release:v1.2.0

sorry, I found that the latest flytepropeller doesn’t use latest flyteplugin which fixes this issue. Let me create a quick pr to bump flyteplugin version in propeller, and I’ll get back to you.

Thanks for the quick responses!

@bumpy-morning-40916 we just merged the pr, and you could update your propeller image to ghcr.io/flyteorg/flytepropeller:v1.1.46 to fix it.

Thanks Kevin! Updated the image