action #18940
closed[opensuse][migration]low disk space warnings on upgrade test from 13.1 to Tumbleweed
Added by dimstar almost 7 years ago. Updated over 6 years ago.
0%
Description
Reference: https://openqa.opensuse.org/tests/398000#step/chrome/23
The 13.1 update to TW leaves very few disk space left which in turn causes the GNOME disk monitor to jump in with a warning. We should try to either have more space available from the beginning on the image or limit the size of the update
Updated by okurz almost 7 years ago
- Subject changed from low disk space warnings on upgrade test from 13.1 to Tumbleweed to [opensuse]low disk space warnings on upgrade test from 13.1 to Tumbleweed
Updated by dimstar over 6 years ago
now it's no longer a warning, but with the latest TW changes (newer kernels, glibc, all together) the space is exhausted:
Updated by okurz over 6 years ago
- Related to action #16016: update 42.1->42.3: installing chrome leaves not enough space on root volume added
Updated by okurz over 6 years ago
- Subject changed from [opensuse]low disk space warnings on upgrade test from 13.1 to Tumbleweed to [opensuse][migration]low disk space warnings on upgrade test from 13.1 to Tumbleweed
- Assignee set to mitiao
@mitiao could you help with this?
Updated by mitiao over 6 years ago
okurz wrote:
@mitiao could you help with this?
yes. I will generate a new 13.1 image with enough space.
Updated by mitiao over 6 years ago
- Status changed from In Progress to Feedback
I don't have permission on o3 and the version 13.1 was not very compatible with openqa nowadays. so the new opensuse 13.1 gnome image was created on my local server with openqa settings and manual intervention.
I uploaded the new image with 40G to our team openqa server which is hosted on a machine in NUE, please download it to o3 for testing:
http://openqa-web.suse.de/tests/108/asset/hdd/openSUSE-13.1-gnome64_40G.qcow2
Tested the image by upgrading without space warning:
zdup from 13.1: http://10.67.17.71/tests/140
update from 13.1: http://10.67.17.71/tests/141
Updated by okurz over 6 years ago
- Status changed from Feedback to In Progress
- Assignee changed from mitiao to okurz
great work, thank you so far! I will download the image to o3 and test. btw, if you want to have permissions to access o3 that should not be a problem in general. IMHO the only prerequisite is that you show up in IRC on #opensuse-factory :-)
wget -O - http://openqa-web.suse.de/tests/108/asset/hdd/openSUSE-13.1-gnome64_40G.qcow2 | ssh o3 "sudo -u geekotest sh -c 'cat - > /var/lib/openqa/share/factory/hdd/fixed/openSUSE-13.1-gnome64_40G.qcow2
openqa_clone_job_o3 501922 HDD_1=openSUSE-13.1-gnome64_40G.qcow2 _GROUP=0
Created job #502215: opensuse-Tumbleweed-NET-x86_64-Build20171009-zdup-13.1-gnome@64bit -> https://openqa.opensuse.org/t502215
Updated by okurz over 6 years ago
succeeded, renamed images on o3:
ariel:/var/lib/openqa/share/factory/hdd/fixed # mv openSUSE-13.1-gnome64{,20171010_out_of_space_on_upgrade}.qcow2 && mv openSUSE-13.1-gnome64{_40G,}.qcow2
retriggered test within the validation group: https://openqa.opensuse.org/tests/502321#live
Updated by okurz over 6 years ago
- Status changed from In Progress to Resolved
looks good, I think we are done here. thx @mitiao
Updated by dimstar over 6 years ago
A negative side-effect (sorry, might not be related, but is well possible):
since this new image is in place, the upgraded system seems to have network connectivity issues, see for example:
https://openqa.opensuse.org/tests/503206#step/consoletest_setup/33
Upgrades from the old 13.1 image to TW did not suffer from this
Updated by dimstar over 6 years ago
- Status changed from Resolved to In Progress
NOTE: I reverted back to the previous disk image - and the network issues post upgrade are recovered (of course the storage issues are back though)
=> the new image is not a 1:1 drop-in replacement
(the newly created image is available as openSUSE-13.1-gnome64_increased-disks-size.qcow2 for now)
Updated by dimstar over 6 years ago
mitiao wrote:
I don't have permission on o3 and the version 13.1 was not very compatible with openqa nowadays. so the new opensuse 13.1 gnome image was created on my local server with openqa settings and manual intervention.
I uploaded the new image with 40G to our team openqa server which is hosted on a machine in NUE, please download it to o3 for testing:
http://openqa-web.suse.de/tests/108/asset/hdd/openSUSE-13.1-gnome64_40G.qcow2Tested the image by upgrading without space warning:
zdup from 13.1: http://10.67.17.71/tests/140
update from 13.1: http://10.67.17.71/tests/141
http://10.67.17.71/tests/141#step/consoletest_setup/32 actually showed the error already too
Updated by mitiao over 6 years ago
- Status changed from In Progress to Feedback
Generated a new one, hope it works:
http://openqa-web.suse.de/tests/111/asset/hdd/openSUSE-13.1-gnome64_40G.qcow2
update_13.1-gnome verified:
http://10.67.17.71/tests/147#step/consoletest_setup/30
Updated by okurz over 6 years ago
- Status changed from Feedback to In Progress
- Assignee changed from mitiao to okurz
verification run looks good, trying again:
wget -O - http://openqa-web.suse.de/tests/111/asset/hdd/openSUSE-13.1-gnome64_40G.qcow2 | ssh o3 "sudo sh -c 'cat - > /var/lib/openqa/share/factory/hdd/fixed/openSUSE-13.1-gnome64_40G.qcow2'" && openqa_clone_job_o3 506988 HDD_1=openSUSE-13.1-gnome64_40G.qcow2 _GROUP=0
Updated by okurz over 6 years ago
the job works fine except in https://openqa.opensuse.org/tests/507763#step/user_gui_login/6 where the user in gdm is not highlighted, compare to https://openqa.opensuse.org/tests/501974#step/user_gui_login/5 . I will retrigger the test to see if this is consistent: https://openqa.opensuse.org/tests/507841
Updated by dimstar over 6 years ago
okurz wrote:
the job works fine except in https://openqa.opensuse.org/tests/507763#step/user_gui_login/6 where the user in gdm is not highlighted, compare to https://openqa.opensuse.org/tests/501974#step/user_gui_login/5 . I will retrigger the test to see if this is consistent: https://openqa.opensuse.org/tests/507841
I've seen this happen with the 'current' disk in Staging updates already too - seems in some cases we don't have a mouse cursor which in turn means it's not in the center of the screen and, as a result, the user not being 'highlighted' with a mouse-over event.
Updated by okurz over 6 years ago
yes, and the retrigger worked: https://openqa.opensuse.org/tests/507841#step/user_gui_login/5
So we again:
mv openSUSE-13.1-gnome64{,20171019_out_of_space_on_upgrade}.qcow2 && mv openSUSE-13.1-gnome64{_40G,}.qcow2
and retriggered -> https://openqa.opensuse.org/tests/507910
got obsoleted by new build, https://openqa.opensuse.org/tests/507948 then
Updated by okurz over 6 years ago
- Status changed from In Progress to Resolved
looks fine, considered done.
@mitiao, thanks again.