-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
v4.4
Update:
Per Max's astute observation in the comment below, the permission issue can be fixed simply by changing the 20 places that call remote_operations.py in evergreen.yml to use the Administrator user instead of $USER. We will likely refactor the code to set an evergreen expansion and merge remote_operations into resmoke as a new subcommand.
Powercycle has been failing on Windows due to an SSH permission issue. There is currently no easy way to investigate the problem due to an inability to access the ec2 instance running the powercycle test.
After chatting with daniel.gottlieb, I'm postponing the work to investigate the permission issue.
- related to
-
SERVER-46294 Update powercycle and jepsen tests to support hygienic build
- Closed
-
SERVER-49333 Use host.create to set up remote instance for powercycle
- Closed
- split to
-
SERVER-48960 Drive powercycle setup commands with expansions.yml
- Closed
-
SERVER-48961 Add an expansion for the powercycle user to evergreen.yml
- Closed