[DRIVERS-2191] Remove use of example.com in Client Side Encryption prose tests Created: 06/Feb/22 Updated: 30/Sep/22 Resolved: 30/Sep/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Kevin Albertson |
| Resolution: | Done | Votes: | 0 |
| Labels: | prose-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Replaces "example.com" with "doesnotexist.invalid" in Client Side Encryption prose tests. This resolves inconsistent test failures observed on ubuntu1804 hosts in the C driver. This may be low priority if teams are not observing test failures. Relevant test changes are in mongodb/specifications@2d52481. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryRemove use of example.com in Client Side Encryption prose tests. MotivationThe Custom Endpoint Test prose test uses the domain "example.com". "example.com" is used to validate a the driver passes a custom endpoint to libmongocrypt. Tests assert that libmongocrypt returns an error including the string "parse error" from responses to example.com. Recently (first observed on 02/06/2022), tests in the C driver evergreen observed HTTP 404 responses from example.com on some AWS signed requests. Here is a repro script run on an ubuntu1804-small spawn host:
Who is the affected end user?DBX engineers running tests with Client Side Encryption. How does this affect the end user?Tests may fail inconsistently. How likely is it that this problem or use case will occur?The C driver Client Side Encryption tests have been failing frequently as of 02/06/2022. If the problem does occur, what are the consequences and how severe are they?Is this issue urgent?Yes. This test failure was observed on 02/04/2022. This may affect all DBX teams. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 07/Feb/22 ] |
|
Author: {'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}Message: Updates test cases 6, 7, 8, and 9 |
| Comment by Kevin Albertson [ 06/Feb/22 ] |