[SERVER-59801] Setting FCV 3.4 in MongoDB 3.6 throws HMAC errors Created: 04/Sep/21 Updated: 05/Sep/21 Resolved: 05/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vinicius Grippa | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, I believe I'm facing a bug. The procedure to trigger the issue is:
My python dummy script:
Following the steps above, the following error is thrown:
I noticed that only if I restart the entire cluster the problem goes away. Since the behavior is erratic, I believe this is a bug. |
| Comments |
| Comment by Dmitry Agranat [ 05/Sep/21 ] |
|
MongoDB 3.6 reached EOL in April 2021 and the SERVER project is for bugs or feature suggestions for supported versions of the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, |
| Comment by Vinicius Grippa [ 04/Sep/21 ] |
|
I know this error in particular is not going to happen from MongoDB 4.0 onwards (since I can't use the FCV 3.4). But it would be important to confirm if downgrading the FCV can lead to problems if the cluster is not restarted. If the restart is needed, then the documentation needs to be updated. |