[SERVER-56273] Update curator hash in powercycle remote host setup Created: 22/Apr/21  Updated: 29/Oct/23  Resolved: 11/Jun/21

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

Type: Improvement Priority: Major - P3
Reporter: Mikhail Shchatko Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-06-28
Participants:
Linked BF Score: 41
Story Points: 1

 Description   

Update curator hash in powercycle remote host setup on older branches.

We use different curator hashes on master and older branches:
117d1a65256ff78b6d15ab79a1c7088443b936d0 on v4.2
b0c3c0fc68bce26d9572796d6bed3af4a298e30e on master

Also we've faced curator setup failures on v4.2, so let's use the same version as on master.



 Comments   
Comment by Githook User [ 11/Jun/21 ]

Author:

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

Message: SERVER-56273 update powercycle curator hash
Branch: v4.2
https://github.com/mongodb/mongo/commit/7bd0cf6c595a330d307a319a394355ded89839af

Comment by Brooke Miller [ 26/Apr/21 ]

robert.guo mentioned he'll sync up with you mikhail.shchatko on this. Thanks for filing it!

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