[SERVER-55548] resmoke.py reports stale "Fixture status" message during fixture teardown Created: 26/Mar/21  Updated: 29/Oct/23  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-72860 Python exceptions in create_fixture_t... Closed
is related to SERVER-50085 Make it easier to correlate mongo pro... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: STM 2021-06-14
Participants:
Story Points: 2

 Description   

The "Fixture status" prefix is cached before the test is run. However, hooks such as CleanEveryN and ContinuousStepdown may restart the MongoDB processes. This leads the teardown fixture test case to log the former pids of the MongoDB processes and can be confusing for Server engineers.

[j2:rs0:n0] | 2021-03-24T17:14:08.089+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":27107,"port":20500,"dbPath":"/data/db/job2/rs0/node0","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[j2:rs0:n1] | 2021-03-24T17:14:09.516+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":27185,"port":20501,"dbPath":"/data/db/job2/rs0/node1","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[j2:rs0:n2] | 2021-03-24T17:14:09.656+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":27265,"port":20502,"dbPath":"/data/db/job2/rs0/node2","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[j2:rs1:n1] | 2021-03-24T17:14:30.891+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":31358,"port":20504,"dbPath":"/data/db/job2/rs1/node1","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[j2:rs1:n0] | 2021-03-24T17:14:30.465+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":31300,"port":20503,"dbPath":"/data/db/job2/rs1/node0","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[j2:rs1:n2] | 2021-03-24T17:14:33.182+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":31498,"port":20505,"dbPath":"/data/db/job2/rs1/node2","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[js_test:explain5] Fixture status:
|ReplicaSetFixture:job2:rs0:node0|j2:rs0:n0|20500|27107|
|ReplicaSetFixture:job2:rs0:node1|j2:rs0:n1|20501|27185|
|ReplicaSetFixture:job2:rs0:node2|j2:rs0:n2|20502|27265|
|ReplicaSetFixture:job2:rs1:node0|j2:rs1:n0|20503|31300|
|ReplicaSetFixture:job2:rs1:node1|j2:rs1:n1|20504|31358|
|ReplicaSetFixture:job2:rs1:node2|j2:rs1:n2|20505|31498|
[ContinuousStepdown:job2] Fixture status:
|ReplicaSetFixture:job2:rs0:node0|j2:rs0:n0|20500|2479 |
|ReplicaSetFixture:job2:rs0:node1|j2:rs0:n1|20501|27185|
|ReplicaSetFixture:job2:rs0:node2|j2:rs0:n2|20502|27265|
|ReplicaSetFixture:job2:rs1:node0|j2:rs1:n0|20503|31300|
|ReplicaSetFixture:job2:rs1:node1|j2:rs1:n1|20504|31358|
|ReplicaSetFixture:job2:rs1:node2|j2:rs1:n2|20505|31498|
[j2:rs0:n0] | 2021-03-24T17:14:47.600+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":2479,"port":20500,"dbPath":"/data/db/job2/rs0/node0","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[ContinuousStepdown:job2] Fixture status:
|ReplicaSetFixture:job2:rs0:node0|j2:rs0:n0|20500|2479 |
|ReplicaSetFixture:job2:rs0:node1|j2:rs0:n1|20501|27185|
|ReplicaSetFixture:job2:rs0:node2|j2:rs0:n2|20502|6812 |
|ReplicaSetFixture:job2:rs1:node0|j2:rs1:n0|20503|31300|
|ReplicaSetFixture:job2:rs1:node1|j2:rs1:n1|20504|31358|
|ReplicaSetFixture:job2:rs1:node2|j2:rs1:n2|20505|31498|
[j2:rs0:n2] | 2021-03-24T17:15:18.748+00:00 I  CONTROL  4615611 [initandlisten] "MongoDB starting","attr":{"pid":6812,"port":20502,"dbPath":"/data/db/job2/rs0/node2","architecture":"64-bit","host":"ip-10-122-66-208.ec2.internal"}
[js_test:elemmatch_object] Fixture status:
|ReplicaSetFixture:job2:rs0:node0|j2:rs0:n0|20500|27107|
|ReplicaSetFixture:job2:rs0:node1|j2:rs0:n1|20501|27185|
|ReplicaSetFixture:job2:rs0:node2|j2:rs0:n2|20502|27265|
|ReplicaSetFixture:job2:rs1:node0|j2:rs1:n0|20503|31300|
|ReplicaSetFixture:job2:rs1:node1|j2:rs1:n1|20504|31358|
|ReplicaSetFixture:job2:rs1:node2|j2:rs1:n2|20505|31498|
[js_test:job2_fixture_teardown] Fixture status:
|ReplicaSetFixture:job2:rs0:node0|j2:rs0:n0|20500|27107|
|ReplicaSetFixture:job2:rs0:node1|j2:rs0:n1|20501|27185|
|ReplicaSetFixture:job2:rs0:node2|j2:rs0:n2|20502|27265|
|ReplicaSetFixture:job2:rs1:node0|j2:rs1:n0|20503|31300|
|ReplicaSetFixture:job2:rs1:node1|j2:rs1:n1|20504|31358|
|ReplicaSetFixture:job2:rs1:node2|j2:rs1:n2|20505|31498|

https://logkeeper.mongodb.org/lobster/build/dd2650c233841c284457e4a5df2d76d1/all#bookmarks=0%2C47851%2C47852%2C47853%2C48185%2C48186%2C48187%2C54129%2C54130%2C54131%2C65990%2C65991%2C65992%2C78604%2C78605%2C78606%2C79341&f~=100~%28Fixture%20status%7C%5C%7CReplicaSetFixture%7CMongoDB%20starting%29&l=1



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 08/Jun/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-55548 update fixture status message before fixture teardown

(cherry picked from commit 0407fb9ea0cceedd89e98907b78a75e650aed5e9)
Branch: v5.0
https://github.com/mongodb/mongo/commit/1189b7861f868fe4f7fbcb463a74ba87b18a5330

Comment by Githook User [ 07/Jun/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-55548 update fixture status message before fixture teardown
Branch: master
https://github.com/mongodb/mongo/commit/0407fb9ea0cceedd89e98907b78a75e650aed5e9

Comment by Robert Guo (Inactive) [ 30/Mar/21 ]

We can move the fixture status table to the fixture class per Raiden's suggestion

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