[SERVER-44743] view_with_invalid_dbname.js must use a try-finally block to ensure deletion of an invalid view Created: 20/Nov/19 Updated: 29/Oct/23 Resolved: 13/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | David Percy |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
In a test failure, this test failed a restartCatalog cmd and consequently left an invalid view in place that would normally be deleted after the restartCatalog cmd. The CollectionValidation hook then found the invalid view. |
| Comments |
| Comment by Githook User [ 13/Dec/19 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: |