Job logging to GCS is broken on 0.50.44 #34556
Labels
area/platform
issues related to the platform
autoteam
community
team/compose
team/platform-move
type/bug
Something isn't working
Helm Chart Version
0.50.55
What step the error happened?
On deploy
Revelant information
We recently upgraded from 0.50.42 to 0.50.44, which caused job logging to stop functioning.
Our deployment is running on GKE Autopilot, with job logging and state storage configured to write to GCS (S3 and minio are fully disabled). This worked fine up until upgrading to 0.50.44, after which the worker and server fail to initialize Log4j due to a failure to validate the (empty) value set for
S3_LOG_BUCKET_REGION
.No configuration other than the version bump has been changed and as mentioned. The logging configuration looks like this:
Adding token (but valid) values for
S3_LOG_BUCKET_REGION
fails due to what appears to be a configuration conflict with having both GCS and S3 configured (partially).Relevant log output
The text was updated successfully, but these errors were encountered: