The build issue in Build (Ubuntu 22.04 Jammy AArch64) is related to Ubuntu Jammy not having access to a IANA Time Zone database so setting TZ=America/Los_Angeles was not working in transformation tests ¹. I've read the Openetelemetry time parsing docs ² which points to how Otel looks for the time zone database.

This issues do seem to be caused by the new way of building the transformprocessor in GoogleCloudPlatform/opentelemetry-operations-collector#350.

I have found two solutions to the issue so far :

• [Best] Add the import _ "time/tzdata" to the transformprocessor/factory.go ³ which will embed the timezone database in every otelopscol build (see ²).
• [Simple, Not the best solution overall] Install tzdata package (contains timezone database) in Ubuntu Jammy tests. I've tried this in e12ded2 and it works.

CC @rafaelwestphal

Update : I found a correct and simple solution for the failure in Build (Ubuntu 22.04 Jammy AArch64) (b/435664151). Some details :

• I've sent Remove time/tzdata and set go version to 1.24 in transformprocessor. opentelemetry-operations-collector#390 for your review. Please approve and update otelopscol to reference this last change in opentelemetry-operations-collector when merged.
• Tested it works in [DNM|TEST] Test different otelopscol commits. #2017.
• Please remove the Dockerfile installation of tzdata in this PR. I will do a followup PR to add tzdata as an Ops Agent dependency.
• Followup PR : [Dockerfile] Add tzdata in Ubuntu build container setup. #2018

Please remove the installation of tzdata in this PR. I will do a followup PR to add tzdata as an Ops Agent dependency.

ops-agent/Dockerfile

Line 818 in a7b7c2f

build-essential cmake bison flex file libsystemd-dev tzdata \

Done