proof validation failed, sector not found in sector set after cron

[phantom-rabbit]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• 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
• 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)
• Other

Lotus Version

The code has changed。

Describe the Bug

I have a sector that has an error in CommitWait.
message in browser：https://filscout.com/en/message/bafy2bzacedrekodgatlqbbfmoejtjo3vu4dlzxwrejz2fckecvj4bmmnrqqna
It looks similar to other successful sectors。

seal.log

It seems that the whole sealing process is normal. My miner code has been modified, but it looks like an error in the chain。

I'm sure my lotus code hasn't changed。

This is a valid data transaction, and I am eager to make it work normally。
Welcome friends with such faults to discuss。

Logging Information

none

Repo Steps

I can't reproduce the problem。

[iseriser]

I do confirm the problem exists.
But lotus-miner sectors update-state --really-do-it [sectorId] CommitFinalize helps

PS: You need to restart miner.
PPS: You may need to execute this command several times.

[iseriser]

More details:

1. If sector is with the following log details - it Finalizes okay!

	proof validation failed, sector not found in sector set after cron
4842.	2022-12-28 09:45:00 +0000 UTC:	[event;sealing.SectorFinalized]	{"User":{}}
4843.	2022-12-28 09:45:00 +0000 UTC:	[error;*xerrors.wrapError]	state machine error: running planner for state CommitFinalize failed: planner for state CommitFinalize received unexpected event sealing.SectorCommitFailed ({User:proof validation failed, sector not found in sector set after cron})
4844.	2022-12-28 09:45:00 +0000 UTC:	[event;sealing.SectorFinalized]	{"User":{}}

2. If sector is with the following log details - it continues to hop between SectorRetryCommitWait and SectorCommitFailed

6785.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorRetryCommitWait]	{"User":{}}
6786.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorRetryCommitWait]	{"User":{}}
6787.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorFinalized]	{"User":{}}
6788.	2022-12-28 09:36:21 +0000 UTC:	[error;*xerrors.wrapError]	state machine error: running planner for state CommitFinalize failed: planner for state CommitFinalize received unexpected event sealing.SectorRetryCommitWait ({User:{}})
6789.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorRetryCommitWait]	{"User":{}}
6790.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorFinalized]	{"User":{}}
6791.	2022-12-28 09:36:21 +0000 UTC:	[error;*xerrors.wrapError]	state machine error: running planner for state CommitFinalize failed: planner for state CommitFinalize received unexpected event sealing.SectorRetryCommitWait ({User:{}})
6792.	2022-12-28 09:36:21 +0000 UTC:	[event;sealing.SectorFinalized]	{"User":{}}

[phantom-rabbit]

thank you , I'll try