bug: Route53 weighted alias cannot be recreated after successful DELETE (dev102) #76
AndreKurait
started this conversation in
Bugs (AWS)
Replies: 1 comment
|
Hi @AndreKurait , thanks for the report. This is now fixed in our latest dev build. Could you run |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A weighted Route53 alias cannot be recreated after a successful DELETE on the current LocalStack Pro dev image. DELETE returns HTTP 200 with INSYNC, and ListResourceRecordSets confirms the exact name/type/SetIdentifier is absent. Recreating the original record nevertheless returns InvalidChangeBatch: already exists.
Reproduced on 2026-10-12 with the unmodified vendor image, its default entrypoint, SERVICES=route53, and no custom extensions/init scripts. The reproduction uses one fresh hosted zone, two ordinary A records as same-zone alias targets, and fictional account 111111111111. No ELB, CloudFormation or application harness is involved.
Environment:
Observed sequence:
Expected: step 6 succeeds after successful deletion. The same tested script subsequently deleted the remaining records and hosted zone without cleanup errors.
The actual error was:
This resembles the previously closed localstack/localstack#12910, but this report supplies a current dev-image weighted-alias reproduction; I have not established that the underlying cause is the same.
Save the following exact tested script as repro.py. A minimal startup command for the same pinned image is below; LOCALSTACK_AUTH_TOKEN should already be set through your normal license workflow. Wait for the Route53 service to be available in /_localstack/health before running the script.
Execute using the bundled SDK (no host port publication is needed):
The script prints each request, response and public record listing, and cleans up its uniquely named hosted zone even after the expected reproduction failure.
All reactions