This message was deleted.
# longhorn-storage
a
This message was deleted.
👍 1
f
I have figured it out - had to upgrade the engine on the volumes, so it won't have to run so many old versions.
You are correct!
The actual problem is that during the upgrade(from the chart) some 1GB volumes have expanded to 3GB and since the PVC is 1GB, there are errors in the UI that it can't turn it back to 1GB. It is very strange as there were only a couple of volumes. Do you know in which repo to file a bug report? longhorn or charts?
You may have hit https://github.com/longhorn/longhorn/issues/5513. The workaround is
expand the PVC to the 3GB
The bug is fixed in Longhorn v1.4.2 though the fix only prevent the issue from happening. For the volumes that are having the problem, you still have to fix them using the workaround above
l
Also @wooden-planet-93714 you can enable automatic engine upgrades to happen on Longhorn upgrade. I’ve had this enabled on production as well as test and dev envs for a long time. Works fine.
w
my problem was from 1.4.1 to 1.4.2 also it was not from 1GB to 10, which is somehow logical, but from 1 to 3 and also one is to 8 where is the automatic engine upgrade setting? I don't see it in the settings section in the UI
f
my problem was from 1.4.1 to 1.4.2
also it was not from 1GB to 10, which is somehow logical, but from 1 to 3 and also one is to 8
@faint-sunset-36608 is investigating this. It is tracking at https://github.com/longhorn/longhorn/issues/6078. Could provide more data in that ticket?
where is the automatic engine upgrade setting? I don't see it in the settings section in the UI
https://longhorn.io/docs/1.4.2/deploy/upgrade/auto-upgrade-engine/