[SERVER-37289] Use authenticated client to run the refreshLogicalSessionCacheNow command in resmoke sharded cluster fixture Created: 24/Sep/18  Updated: 29/Oct/23  Resolved: 30/Nov/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.10

Type: Task Priority: Major - P3
Reporter: Yves Duhem Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-36152 Update requirements.txt Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2018-12-17
Participants:
Linked BF Score: 50
Story Points: 1

 Description   

To be able to use PyMongo 3.6+ with resmoke, we need to use an authenticated client to run the refreshLogicalSessionCacheNow. Since PyMongo 3.6+ will use implicit sessions, if the command is run unauthenticated then we hit SERVER-34820 and fail with a "there are no users authenticated" message.



 Comments   
Comment by Githook User [ 30/Nov/18 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-37289 Work around how refreshLogicalSessionCacheNow requires auth.
Branch: v3.6
https://github.com/mongodb/mongo/commit/2734b452c2eb4cecc8c0dc1d21152488abfbaee6

Comment by Blake Oler [ 30/Nov/18 ]

This has been making a decent amount of noise in 3.6 builds. Is it possible we could schedule this soon? max.hirschhorn

Comment by Max Hirschhorn [ 24/Sep/18 ]

Per a Slack conversation with ben.caimano, the plan is for SERVER-36152 to not upgrade the version of PyMongo we're running. This would be problematic on Windows because we aren't always installing additional dependencies into a virtual environment and are instead sometimes installing additional dependencies into the system Python.

yves.duhem, with regard to the refreshLogicalSessionCacheNow command, we could also backport the requiresAuth()-related changes from 85dc8dd as part of SERVER-34653. This came up on jack.mulrow's code review for backporting SERVER-32604 to the 3.6 branch and he is planning to follow up with the Platforms team about this. More explicitly, we would only need to change resmoke.py to auth on the 3.6 branch if we don't plan on changing the server's behavior on the 3.6 branch. There shouldn't be any issue with the refreshLogicalSessionCacheNow command, logical sessions, and auth on later branches.

Generated at Thu Feb 08 04:45:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.