Name of Failure:

TestClientSideEncryptionProse/11._kms_tls_options_tests/aws
TestClientSideEncryptionProse/11._kms_tls_options_tests/azure
TestClientSideEncryptionProse/11._kms_tls_options_tests/gcp
TestClientSideEncryptionProse/11._kms_tls_options_tests/kmip

Link to task:

https://spruce.mongodb.com/task/mongo_go_driver_kms_kmip_test__version~7.0_os_ssl_40~rhel87_64_test_kms_kmip_ed56f8a95f78e85c245dfc6f04346236434e3d84_24_08_28_14_56_24/tests?execution=0&sortBy=STATUS&sortDir=ASC

Context of when and why the failure occurred:

This is seemingly related to GODRIVER-3228, but in that case the kmip variant was failing while the other KMS tests were failing because a different certificate authority file was being used. I confirmed that the correct pem files are being used throughout, and that the tls options are being applied to validClientEncryptionOptionsWithTLS, but it seems that no certificate is actually being applied. This may be due to the change in the options builder pattern.

Stack trace:

 [2024/08/09 14:24:55.034]     client_side_encryption_prose_test.go:1641: 
 [2024/08/09 14:24:55.034]         	Error Trace:	/data/mci/bbbf9f55c3c39d48fbb29b304a7c3b37/src/go.mongodb.org/mongo-driver/internal/integration/client_side_encryption_prose_test.go:1641
 [2024/08/09 14:24:55.034]         	            				/data/mci/bbbf9f55c3c39d48fbb29b304a7c3b37/src/go.mongodb.org/mongo-driver/internal/integration/mongotest.go:268
 [2024/08/09 14:24:55.034]         	Error:      	Should be true
 [2024/08/09 14:24:55.034]         	Test:       	TestClientSideEncryptionProse/11._kms_tls_options_tests/gcp
 [2024/08/09 14:24:55.034]         	Messages:   	expected error 'tls: failed to verify certificate: x509: certificate signed by unknown authority' to contain 'HTTP status=404'