Closed jochenehret closed 1 week ago
I encounter same issue in stemcell 1.486.
What sort of compilation VMs are you using? The default for a bbl environment I imagine?
I suspect this regression was caused by a change in the packaging script that synchronized debuginfo levels with Percona's debug levels. This probably increased the memory required for compilation and we didn't notice in our CI pipelines where we've increased the size of our compilation vms to speed up these slow compile jobs.
The BOSH cloud config is printed in the logs of the "deploy-cf" task: https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/update-releases/jobs/update-pxc/builds/33
This is the compilation VM configuration:
compilation:
az: z1
network: private
reuse_compilation_vms: true
vm_extensions:
- 100GB_ephemeral_disk
vm_type: e2-highcpu-4
workers: 6
If you're confident that the compilation will succeed with more memory, we can adapt the cloud config.
I was able to reproduce this in our environment with the e2-highcpu-4
compilation vm type.
In the short-term, I do think a larger compilation vm would avoid this issue.
Our pipelines are currently using an e2-highcpu-8
rather than e2-highcpu-4
and have not experienced this issue:
az: z1
network: private
reuse_compilation_vms: true
vm_extensions:
- 100GB_ephemeral_disk
vm_type: e2-highcpu-8
workers: 6
Long-term, we do have a story to investigate further optimizations to reduce the resource requirements for compilation.
Ok, I'll adapt the cloud-config for the test environment!
With e2-highcpu-8
the compilation succeeds:
https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/update-releases/jobs/update-pxc/builds/34
Thanks for the hint, closing the ticket.
Bug Report Info
Currently:
pxc-release v1.0.30 does not compile on Ubuntu Jammy stemcell v1.423.
Expected:
It should compile successfully.
Steps to Reproduce:
The failure happens in the "update-releases" pipeline: https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/update-releases/jobs/update-pxc/builds/33
Deployment Context:
Error happens already at compile time.
Reference: