WDPost / WinningPost workers are used for transfers of finalized sectors

[RobQuistNL]

Checklist

• [X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• [X] This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• [X] This is not a new feature request. If it is, please file a feature request instead.
• [X] This is not an enhancement request. If it is, please file a improvement suggestion instead.
• [X] I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• [X] I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• [ ] I did not make any code changes to lotus.

Lotus component

• [ ] lotus daemon - chain sync
• [ ] lotus miner - mining and block production
• [ ] lotus miner/worker - sealing
• [X] lotus miner - proving(WindowPoSt)
• [ ] lotus miner/market - storage deal
• [ ] lotus miner/market - retrieval deal
• [ ] lotus miner/market - data transfer
• [ ] lotus client
• [ ] lotus JSON-RPC API
• [ ] lotus message management (mpool)
• [X] Other

Lotus Version

v1.15.2-rc1

Describe the Bug

When running a wdpost and winningpostworker on a machine, I'm suddenly starting to see GET jobs on that machine.

I was expecting these workers to do nothing except wd / winningpost. They should not be used to move sealed sectors from other workers to long term storage.

Logging Information

-

Repo Steps

1. Run wdpost / winningpostworker
2. See GET job appear on these workers when finalizing

[lanpin]

wdpost and winpost worker don't attach store path.

[RobQuistNL]

True, I mislooked - but since I started this one I saw some GET's on some machines that I was not expecting. But all is good :)