Issue with Upgrade from 9.0.2 to 9.0.3 - Failed to remove directory: Directory not empty

[joecoolio66]

Prerequisites

• I understand and accept the project's code of conduct.
• I have already searched in existing issues and found no previous report of this bug.

Describe the bug and add attachments

I reported this issue last September and it was referred to autoupgrade#1523 as a potential fix, but I can confirm that I received this error today upgrading 9.0.2 to 9.0.3. Afterwards we had to apply the SQL on the update manually to the DB (luckily it was only 1 query) and also luckily we keep our site up to date so no modules needed to be updated.

Why is this error still happening? What can we do to avoid it in the future? It's like roulette updating. We updated our backup fine.. this error occurred only in our PROD. The same situation as last time.

Expected behavior

No response

Steps to reproduce

Run the Update Assistant (7.5.1) and try updating 9.0.2 to 9.0.3. It appears that this error is somewhat random

PrestaShop version(s) where the bug happened

9.02

How you installed PrestaShop

Update Assistant

PHP version(s) where the bug happened

8.4

Your company or customer's name goes here (if applicable).

No response

[joecoolio66]

Reference to my other bug report which is now closed: PrestaShop/PrestaShop#39509

[Quetzacoalt91]

This issue appears when ajax requests are sent to the shop when the update is running. Among them, we find the check of notifications to display at the top of the page.

The tab running the update won't send these ajax requests, but if you have other pages opened at the same time, they will still send these ajax requests which can impact the process.

Can you close the other tabs opened on the store while the update is running?

[Touxten]

Hello @Quetzacoalt91
What do you think about adding this information somewhere?
I always have several tabs open in the BO.

[Quetzacoalt91]

The best solution would be to have a maintenance mode for the BO as well, but yeah, you got a good idea.

[joecoolio66]

I thought this issue was supposed to be addressed in #1523. Will this be re-addressed for future releases?

[Quetzacoalt91]

It's been addressed. We have fixed an issue on the page that runs the update, but if you keep other tabs opened, the issue may still occur. Hence the need to close everything before starting the update.

[AureRita]

Hi @joecoolio66

Thank you for your report, As you said, this issue is now a know issue, we'll add this information in a discussion to let the information in a link accessible from the module UI.

Thank you !