[SERVER-41194] Run passthrough tests under an alternate horizon Created: 16/May/19  Updated: 07/Jun/19  Resolved: 07/Jun/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: ADAM Martin (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Dev Tools 2019-06-03, Dev Tools 2019-06-17
Participants:

 Description   

We should stand up a test suite that runs an entire suite of tests under an alternative horizon name to ensure that behavior doesn't vary with the selected horizon.



 Comments   
Comment by ADAM Martin (Inactive) [ 07/Jun/19 ]

This is not going to be feasible. It requires communicating with localhost under multiple names, which our testing infrastructure is not setup for.

Comment by Andrew Morrow (Inactive) [ 06/Jun/19 ]

adam.martin - Ping on closing this?

Comment by Andrew Morrow (Inactive) [ 04/Jun/19 ]

adam.martin - Given what you said above, should we close this out as won't fix?

Comment by ADAM Martin (Inactive) [ 24/May/19 ]

We'd require access to the host under two different names, similar to the HOSTALIASES feature. Further, split horizons requires SSL/TLS with multiple SANs in the server certificate. I don't think that we can globally apply this to all replication tests, can we? It might be more useful to modify just a few critical replication tests to test their operation under the Split Horizons feature.

Comment by Max Hirschhorn [ 19/May/19 ]

Max Hirschhorn Is it possible that we could run all of the tests of replication in another passthrough suite using dual hostnames for localhost? Further, can we get some common configuration injected into those tests?

I'm not entirely sure what is involved in having "dual hostnames for localhost." Is this related to how henrik.edin is using the HOSTALIASES environment variable in SERVER-40645? Until I know more, I'll just point you to the ReplicaSetFixture.setup() method for how the replSetInitiate and replSetReconfig commands are run when resmoke.py starts a new replica set. It sounds like there's some extra configuration you'd like to do which we can hide behind some kind of flag (either specified as a YAML or command line option).

Comment by ADAM Martin (Inactive) [ 17/May/19 ]

max.hirschhornIs it possible that we could run all of the tests of replication in another passthrough suite using dual hostnames for localhost? Further, can we get some common configuration injected into those tests? This would permit us to setup all of the tests to run in a horizon, and see that they all pass.

Generated at Thu Feb 08 04:57:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.