Name truncation causes name collisions in GCP (bosh-lite patches)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- terraform
- Domain
- cloud
Research direction
Start with plan-patches/bosh-lite-gcp/terraform/bosh-lite.tf, especially the name prefix on the firewall resources at lines 1-3 and the resources at lines 5 and 33. Confirm whether the truncation is specific to this patch or broader, then ensure concurrent bbl environments produce unique names while all firewall names remain within GCP's 63-character limit.
Written by the indexing model from the issue text.
Description
Creating an issue instead of a PR since I'm not sure whether this issue is limited to plan-patches/bosh-lite-gcp/terraform/bosh-lite.tf or should be addressed more broadly.
With two concurrent bbl up runs that happened to draw the same lake name (qinghai) in the same year (2026), two distinct bbl envs can produce the identical 20-char prefix bbl-env-qinghai-2026
Increasing the prefix to 32 characters includes the full date+hour (bbl-env-qinghai-2026-06-02t01-27z) making every concurrent run's firewall names globally unique, while staying within GCP's 63-character resource name limit (32 + the longest suffix -bosh-director-lite-tcp-routing = 63 chars exactly).
│ Error: Error creating Firewall: googleapi: Error 409: The resource 'projects/cloud-foundry-310819/global/firewalls/bbl-env-qinghai-2026-bosh-director-lite' already exists, alreadyExists
│
│ with google_compute_firewall.bosh-director-lite,
│ on bosh-lite.tf line 5, in resource "google_compute_firewall" "bosh-director-lite":
│ 5: resource "google_compute_firewall" "bosh-director-lite" {
│
╵
╷
│ Error: Error creating Firewall: googleapi: Error 409: The resource 'projects/cloud-foundry-310819/global/firewalls/bbl-env-qinghai-2026-bosh-director-lite-tcp-routing' already exists, alreadyExists
│
│ with google_compute_firewall.bosh-director-lite-tcp-routing,
│ on bosh-lite.tf line 33, in resource "google_compute_firewall" "bosh-director-lite-tcp-routing":
│ 33: resource "google_compute_firewall" "bosh-director-lite-tcp-routing" {
- Dominant language
- Go
- Stars
- 181
- Forks
- 179
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudfoundry/bosh-bootloader
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
cloudfoundry/bosh-bootloader#701 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cloudfoundry/bosh-bootloader#698 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cloudfoundry/bosh-bootloader#676 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cloudfoundry/bosh-bootloader#641 · 2 comments ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 50/100
cloudfoundry/bosh-bootloader#636 · 2 comments ·
All issues in cloudfoundry/bosh-bootloader
Similar issues
-
agent-butler-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jordansmall/spindrift#6414 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Icinga/icinga-kubernetes#294 ·
Maintainers usually reply within 4 days
-
Cluster details: the Control Plane version field has a different border color than its icon boxOpenkind/design sig/ui
Difficulty 1/5 Under an hour Newbie friendliness 92/100
kubermatic/dashboard#8449 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
filecoin-project/curio#1632 ·
Maintainers usually reply within 1 day