Noble stemcell validation for cf-deployment #1224
Description
What is this issue about?
We want to validate cf-deployment on a "Noble" beta stemcell release. The set up of community validation pipeline can be found here: https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/noble-stemcell-validation. Here is a PR for the corresponding validation pipeline: #1219.
The pipeline relies on stable-bellatrix bbl env. Next, it deploys CF followed by smoke-tests and the CF acceptance tests. The pipeline is triggered when a new "Noble" stemcell is available on bosh.io
This parent issue will be used to track child issues that are raised for the involved BOSH releases.
Issues
- pxc-release v1.0.33 fails to compile on Ubuntu Noble stemcell v0.26 pxc-release#54
- "rep" fails on Ubuntu Noble stemcell diego-release#979
- Pushing application fails with BuildpackCompileFailed on Ubuntu Noble stemcell java-buildpack#1099
- Pushing a ruby application fails with DNS server misbehaving Ubuntu Noble stemcell diego-release#987
- bosh-dns noble support bosh-dns-release#99
- Application is not able to retrieve container metrics for memory usage on Ubuntu Noble stemcell diego-release#995
- Cloud Foundry bosh deploy with Noble stemcell is failing sporadicly on BBL environment bosh-deployment#486
PRs
- Exclude noble stemcell from release notes for now runtime-ci#451
- Add "bellatrix" to automatic certificate regeneration app-runtime-deployments-infrastructure#5
- Add "noble" stemcell to BOSH addons #1223
- Use Postgres for noble-stemcell-validation pipeline #1222
- Fix noble-stemcell pipeline #1221
- validation pipeline for the new beta Noble stemcell #1219
- Fix BOSH DNS config in Noble stemcell ops file #1236