Open toddr opened 1 year ago
The only thing special about my system is that I have a 500MB /boot partition. However the error message doesn't seem to indicate this is related to my problem.
Setting export LEAPP_OVL_SIZE=3000
seems to have fixed my problem. Is there a way to pass this on command line or should this value be increased by default from 2048?
export this : LEAPP_OVL_SIZE=8192
What is that environment variable controlling? I have a similar error (reporting an error that "At least 317MB more space needed on the / filesystem" on a system with 64G free on /) and setting LEAPP_OVL_SIZE=8192 did not correct that error. I also have a 500MB boot partition, but I removed two old kernels to increase the free space on /boot to 394MB, and the amount of free space needed message did not change even though I freed 120MB on /boot. The message also did not change after I freed about 6G on /, so I do not think the message actually relates to free disk space in any way.
I tried again, but from su rather than sudo (previously I was logged in as a user and used sudo to run leapp preupgrade and leapp upgrade, I ran again after using su to login as root) and was able to finish leapp upgrade with no errors. Perhaps I did something else differently, but that is not clear to me right now.
We were having exactly the same issue as you. Executing without sudo let us finally upgrade. What we noticed: LEAPP_OVL_SIZE was not taking into account when using sudo. We could check that the overlays were created 2.0GB in size.
Were you using the --preserve-env
option with sudo? If not I can see why just exporting the environment variable first wouldn't really do anything for you.
Read the manual page for sudo
for more information on how environment variables work under sudo
.
Since the work around did work once I figured out the environment issues caused by sudo, what do I need to do to mark this as solved? I am not familiar yet with how AlmaLinux manages github issues.
Since the work around did work once I figured out the environment issues caused by sudo, what do I need to do to mark this as solved? I am not familiar yet with how AlmaLinux manages github issues.
We don't believe sudo has anything to do with the originally reported issue. I don't think this should be closed with "sudo is the fix". Last I recall, we believe this has to do with mount points.
Sorry, maybe I left out too much context. The original problem has nothing to do with sudo, that is correct. The problem is related to the overlay filesystem running out of allocated space. The work around is to export LEAPP_OVL_SIZE=8192 to increase the overlay filesystem space. I originally could not get that work around working properly because I did not understand how environment variables were passed when using sudo. I changed to just su into root account, then exported that environment variable and ran leapp, and that did work. So should this get closed with indication that the work around is successful, or should it stay open because it indicates that leapp needs to change the default settings so the work around isn't needed?
IMO the default is too low. Especially if there's sufficient disk space.
On my CentOS 7 system with 34GB of free space, I am getting the following failure during a leapp upgrade: