Blocked startup after upgrade with FileExistsError

[cociweb]

What version of Music Assistant has the issue?

2.4.0b20

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

• Yes

The problem

Hello,

I've tried to update my setup with preserved settings from 2.3.6 to 2.4.0b20. Unfortunatelly the MA does not starts and the atached log is arrived.

How to reproduce

update the docker image from 2.3.6 and do not purge the /data

Music Providers

several

Player Providers

several

Full log output

2025 01 26 01 12 15 690.txt

Additional information

Reverting back to stable (2.3.6) does not solved the problem.... The 2.3.2 oldstable start was not blocked....

What version of Home Assistant Core are your running

What type of installation are you running?

Standalone

On what type of hardware are you running?

Linux

[OzGav]

Did you see the warning at the bottom of here? https://www.music-assistant.io/release/

[OzGav]

This will be closed soon

[cociweb]

okay understandable. so it is a known issue?
I just would have to draw the attention to the importance of the update test before the final 2.4.0 version.

[marcelveldt]

How did you attempt this ? You cant switch between beta and stable addon with keeping the data.
Beta and stable add-on will have their own data.

[cociweb]

docker pull ...:stable vs ....:beta (I've modified the report file, as it is HA independent (standalone MA server).

[marcelveldt]

OK, in that case be aware that the access rights are the same (this smells like some access rights issue) if you go from stable to beta and you CAN NOT go back from beta to stable.

[cociweb]

ok, I've made another try:
I've tried to start the latest beta (2.4.0b23) with the same behaviour. then I've removed the whole data/.cache folder and during the startup it is recreated again. now the rolling back to the latest stable (2.3.6) is okay.

except I've lost my old collages (2x2 size) and the new 6x6 is recreated.

it is worth to mention that I preserve my setting/cache from the very first of the v2betas.

Anyways, the ownership and the access right attributes are the same for the old and the newly generated cache database&collages.

please note that the newly created folders remained the same as earlier: /data/.cache/collated_images/. I've observed some magic in 2.3.3 and I think thats why the 2.3.2 is worked. As I see, with 2.4.0b23 it is evoluted and it should be /collated/ but it is remained as earlier.

Maybe in this case we need to introduce a forced cache purge as a workaround?

[marcelveldt]

I checked the code and the only reason you (as the only one) running into this is because you have been going back and forth in versions using the same data folder which we do not support, especially not between beta and stable. We support going forward, but not backward. Going back in the same major version will probably work but switching between major not.