4.0.3 to 4.0.4 only changed how we authenticate to the Stable channel, see:
So I think this may be unrelated. Have you tried a reboot since the upgrade. It may be that you have part old and part new code running. Although an update by the suggested means (last fix workaround for Stable) or via Web-UI should avoid this happening. Let us know how you get on. And journalctl logs at time of the failed request may be informative. Do you have a lot of shares possibly, i.e > 9000 as we had a recent change to getting 32,0000 of ‘things’ rather than the prior 9,000 in 4.0.2-0:
And does it take say a minute and a half before this message appears by chance. So more info would be good on that front.
Thanks for the report thought. But we haven’t had any similar reports, at least not just yet. Fingers crossed .
And incidentally, as you don’t say which version you upgraded from, our even earlier release candidate was 4.0.1-0 which only changed the syntactic formating of the python code:
Also I’ve assumed here you are running an install from the DIY installer, or a hand configured Leap 15.2 as per the dev notes. We are no longer CentOS compatible with regard to sub-volume parsing.
.