PHPC-1015: Add test for DNS Initial Seedlist

[derickr]

https://jira.mongodb.org/browse/PHPC-1015

We'll need to decide whether we want to always run this. Starting up a whole
replicaset for one test is a waste of resources really. It also requires that we add a line in our /etc/hosts files (with the IP address of the Vagrant host) for this to work.

[jmikola]

It also requires that we add a line in our /etc/hosts files (with the IP address of the Vagrant host) for this to work.

Is this required change documented anywhere? Perhaps it can be added in a block comment within the test?

Am I correct to assume that the test fails without the /etc/hosts change in place?

I think it's worth having the Vagrant environment committed. We can probably leave this as a manual test for the time being and revisit once we can move over to Evergreen. To that end, a separate tracking ticket associated with the Evergreen epic and also linked to PHPC-1015 would be helpful.

[jmikola]

Interesting. Is this necessary because we do not include ReadCommandLineArguments.m4? AFAIK, this is one of the few times we have to set a variable this way (instead of using AC replacement).

[derickr]

Yup.

[derickr]

Is this required change documented anywhere? Perhaps it can be added in a block comment within the test?

No, but I can add that.

Am I correct to assume that the test fails without the /etc/hosts change in place?

Yes:

Fatal error: Uncaught MongoDB\Driver\Exception\ConnectionTimeoutException: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling ismaster on 'localhost.test.build.10gen.cc:27018'] [connection refused calling ismaster on 'localhost.test.build.10gen.cc:27017'] in /home/derick/dev/php/derickr-mongo-php-driver/tests/connect/bug1015.php:7
Stack trace:
#0 /home/derick/dev/php/derickr-mongo-php-driver/tests/connect/bug1015.php(7): MongoDB\Driver\Manager->selectServer(Object(MongoDB\Driver\ReadPreference))
#1 {main}
  thrown in /home/derick/dev/php/derickr-mongo-php-driver/tests/connect/bug1015.php on line 7

I think it's worth having the Vagrant environment committed. We can probably leave this as a manual test for the time being and revisit once we can move over to Evergreen. To that end, a separate tracking ticket associated with the Evergreen epic and also linked to PHPC-1015 would be helpful.

Not sure how easy this is going to be with Evergreen either, but: https://jira.mongodb.org/browse/PHPC-1054