Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The step file is getting left around after finalize() #566

Open
joshtrichards opened this issue May 26, 2024 · 2 comments
Open

The step file is getting left around after finalize() #566

joshtrichards opened this issue May 26, 2024 · 2 comments

Comments

@joshtrichards
Copy link
Member

This doesn't look right:

2024-05-25T05:44:01+0000 RnQG5qanp7 [info] POST request for step "12"
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] startStep("12")
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] finalize()
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] storage location: /data/updater-ociz9efdik2y/downloads/nextcloud/
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] call opcache_reset()
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] end of finalize()
2024-05-25T05:44:01+0000 RnQG5qanp7 [info] endStep("12")

finalize() does the cleanup - removing the .step file - then we're also calling endStep("12") again somehow according to our logs. This re-adds a .step file again, stuck in step 12.

First seen while troubleshooting some updater issues on the forum, then reviewed the logs from running tests. Indeed.

@joshtrichards
Copy link
Member Author

I think the only reason this hasn't been a bigger problem is because the Updater (in server) repair steps also clean-up the .step file in most cases.

@joshtrichards
Copy link
Member Author

I guess we should separate out the .step removal from step 12 so it's always the very last thing done. That way we don't have to rely on the repair step.

Admittedly, the repair step should basically always run if the occ upgrade / doUpgrade() completes, but it's odd we're both removing the file in the Updater then immediately (accidentally) recreating it then relying on the post-Updater upgrade to clean up again.

Though the real cause of the issue I was looking into that turned up the above I suspect is: #567

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant