bug: ELBv2 DeregisterTargets rejects an absent target instead of succeeding idempotently #61
Closed
AndreKurait
started this conversation in
Bugs (AWS)
Replies: 0 comments
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.
Uh oh!
There was an error while loading. Please reload this page.
Additional version check — 2026-10-08
Verified fixed in 2026.8.1. Both absent-target deregistration calls now return HTTP 200 and the empty target-group membership is unchanged. The original 2026.7.5 failure remains documented below. I am closing this report as resolved for the verified newer version; no backport or further maintainer action is requested.
The comparison used an unmodified
localstack/localstack-pro:2026.8.1Linux ARM64 image,repository digest
sha256:4aef81c531684570d7b3cfd2805afa02194c929d52bbeedabb7d4874798b1572.Vendor packages were
localstack-core 2026.8.1,moto-ext 5.1.48, and bundledboto3/botocore 1.43.78. HTTP probes used a separateboto3/botocore 1.43.101client; the process-local security-group probe used the bundled interpreter.
The same scripts were used, with no custom extensions or provider source changes.
Owned test containers and the disposable network were removed.
This is a second specifically tested version, not a claim to have tested the latest release.
Existing report search
I searched the LocalStack issue tracker and current organization Discussions for this operation and failure. I did not find an existing report for this exact reproduction.
Current behavior
Create a disposable VPC and an empty instance target group, then call
DeregisterTargetstwice for the same syntactically valid absent instance ID. Both calls return HTTP 400InvalidTarget, indicating that the target does not exist or is not in the same VPC. Target-group membership remains empty.This is a public API reproduction against a fresh, unmodified LocalStack container. No custom extension or source patch is involved.
Expected behavior
Both calls should return HTTP 200 and leave the group empty. The AWS API explicitly documents successful deregistration when the specified target does not exist.
Reference: DeregisterTargets.
An unknown target group should still fail. This report is specifically about an absent target in an existing target group, not malformed requests or connection-draining timing.
Environment
localstack/localstack-pro:2026.7.5.sha256:0d74e1d2d7ce13a3cb25fc64cf15eb225f1c95c762e56e057bc6a9ed0ed29306.localstack-core 2026.7.5,moto-ext 5.1.46,moto.__version__ = 5.1.21.dev,boto3/botocore 1.43.51.Fresh confirmation on 2026-10-08: the same discrepancy reproduced on Linux ARM64 against the same unmodified image, using a separate
boto3/botocore 1.43.101client. The disposable container and network were removed after the run. The startup block below includes the run's disabled DNS listener/default EC2-image downloads and temporary state storage; no provider source or extension was changed.Steps to reproduce
Start a disposable instance on a free loopback port:
Run the block in a disposable shell. Port 4567 must be free. The client needs
boto3; it uses only dummy credentials and a loopback endpoint. It creates disposable resources and cleans them up infinally; the shell trap removes the container even when the script reports failure. A nonzero exit is expected while the reported discrepancy is present. No Docker socket mount or application services are required.Complete standalone reproducer: elbv2_deregister_absent_target.py
All reactions