From: sergiyvamz (@sergiyvamz) <noreply+sergiyvamz@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] issue #2254: [bg plugin] Pods stick in POST phase permanently after a Blue/Green switchover completes, due to a race between post-COMPLETED monitor reset and the lingering final status row in mysql.rds_topology
Date: Thu, 19 Nov 2026 16:37:43 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2254-c7015482610@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2254@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2254@github.com>
Hi @seoh10,
Thanks for the detailed report, and please pass our thanks to AWS Support for the analysis and reproduction.
This issue is fixed by #2242, which has been merged into `main`. After a completed switchover, a context that never saw the deployment in the `CREATED` phase now ignores a lingering `POST`/`COMPLETED` status row, so it stays in idle monitoring and can detect a new deployment. The switchover timeout is also now started in every phase from `PREPARATION` onwards, so a stuck switchover is always bounded.
The fix will be included in the next release. If you'd like to verify it earlier, you can try the latest snapshot build of `main`. We'll close this issue once the release is out, unless you see the problem again.
Thank you for your patience!