Deal stuck in StorageDealClientTransferRestart state

[dineshshenoy]

Describe the bug
A deal from Textile has been stuck in StorageDealClientTransferRestart for 5 days, even though the Lotus version was recently upgraded. This is happening with a PL'miner (run by Marcus) - f02665

DealDate: Nov 5 21:22:44
DealCid: bafyreih7ayfw3kdhwxavriwbt5lnv3xdtvuhocd5y4zgu7jg3wlaxfd7oa
DealId: 0
Provider: f02665
State: StorageDealClientTransferRestart
On Chain? N
Slashed? N
PieceCID: baga6ea4seaqdqskn6z4sfnnkxluokxfcvkhkhd6szowspnumsmc5j5zrwlkluaa
Size: 7.938 GiB
Price: 0.00208142 FIL
Duration: 520355
Verified: false

Version (run lotus version):
lotus version 1.1.2+git.f225b7b92

Additional context
Deals are being tracked here: http://13.68.239.146:9090/deals.txt and updated every 10 minutes

[hannahhoward]

@dineshshenoy I believe this will be fixed with the new data transfer release, though it may not unstick previous deals. The new data transfer release will be merged here: #4730

[dineshshenoy]

Terrific - @jsign this sounds consistent to what you've experienced. When you ran another deal, we presumably didn't encounter #4789 but got blocked on #4790

[dineshshenoy]

@jsign - can you retry the same payload for the DeaalCid above to verify?

[jsign]

I'd think I need to wait for #4730 to get merged to master, right?
I'm already subscribed to the PR, so I'll know as soon as gets merged.

[jsign]

Looks merged, will give it a try.

[jennijuju]

@jsign could you please update the status of this tickets after you give it a try?

[jsign]

After updating, those deals still have in the same status. I'm not sure if the update should unblock existing deals, or may fix this in new ones.

Creating a new fresh deal lead to another situation #4805.

[dineshshenoy]

Closing since I don't think it's happening anymore. @hannahhoward said old deals may not restart but new deals now experience #4805

[kernelogic]

All my new deals are stuck at StorageDealCheckForAcceptance state. No progress for 2 days. Using the latest lotus 1.2.1.

[dirkmc]

@kernellogic let's move this conversation to #4790