[SERVER-63073] Fix ShardNotFound handling in shard_removal_triggers_catalog_cache_invalidation.js Created: 28/Jan/22  Updated: 29/Oct/23  Resolved: 08/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.2.0, 4.2.17, 5.0.5, 4.4.12
Fix Version/s: 5.3.0, 5.0.7

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0, v4.4, v4.2
Sprint: Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 41

 Description   

The test is trying to handle the non-idempotency of removeShard (SERVER-32553) by checking for ShardNotFound error . However, the check is wrongly preceded by an assert.CommandWorked that throws before being able to check the error code.



 Comments   
Comment by Githook User [ 16/Feb/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-63073 Fix ShardNotFound handling in shard_removal_triggers_catalog_cache_invalidation.js

(cherry picked from commit 24b8de69f84c49e406fc534a33ee1574c13e23b9)
Branch: v5.0
https://github.com/mongodb/mongo/commit/985d83b45b397c3b9ec0f2faca2127faad2e6d74

Comment by Githook User [ 08/Feb/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-63073 Fix ShardNotFound handling in shard_removal_triggers_catalog_cache_invalidation.js
Branch: master
https://github.com/mongodb/mongo/commit/24b8de69f84c49e406fc534a33ee1574c13e23b9

Generated at Thu Feb 08 05:56:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.