-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: SDAM
-
None
-
Needed
-
Summary
Test SDAM does not remove a secondary reporting "me":"[::1]:27017" when connecting the URI mongodb://[::1]:27017.
Motivation
This is a regression test for the issue noted in this comment of HELP-68823. Adding a spec test for IPv6 literals may verify this behavior works in all drivers.
Who is the affected end user?
Users connecting with IPv6 literals.
How does this affect the end user?
In the case of HELP-68823, the secondary was removed from the topology. This resulted in the client being unable to connect.
How likely is it that this problem or use case will occur?
(Hopefully) unlikely. I expect this would not occur if a driver represents the address as a literal string. This is fixed in the Rust driver, but may be untested in other drivers.
If the problem does occur, what are the consequences and how severe are they?
Failure to connect.
Is this issue urgent?
No?
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
Acceptance Criteria
Test SDAM processing IPv6 literals. Ensure the test fails on the Rust driver before the fix and passes after.
- split to
-
GODRIVER-3503 Test IPv6 literal in SDAM
-
- Needs Triage
-
-
NODE-6835 Test IPv6 literal in SDAM
-
- Backlog
-
-
RUBY-3632 Test IPv6 literal in SDAM
-
- Backlog
-
-
CSHARP-5521 Test IPv6 literal in SDAM
-
- Ready for Work
-
-
CDRIVER-5926 Test IPv6 literal in SDAM
-
- Closed
-
-
CXX-3247 Test IPv6 literal in SDAM
-
- Closed
-
-
MOTOR-1440 Test IPv6 literal in SDAM
-
- Closed
-
-
PHPLIB-1641 Test IPv6 literal in SDAM
-
- Closed
-
-
PYTHON-5194 Test IPv6 literal in SDAM
-
- Closed
-
-
RUST-2175 Test IPv6 literal in SDAM
-
- Closed
-
-
JAVA-5810 Test IPv6 literal in SDAM
-
- Investigating
-