action #15406
closedTumbleweed and Leap upgrade cases now run out of space
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-42.1-kde@64bit fails in
yast2_i with an obvious error message
Reproducible¶
Fails since (at least) Build 20161208 and also in different scenarios since some more days.
Expected result¶
Probably a "green" job can only be expected when the original disk image is replaced by one with more space.
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 8 years ago
- Subject changed from Tumbleweed upgrade cases now run out of space to Tumbleweed and Leap upgrade cases now run out of space
- Priority changed from High to Urgent
Also happens for Leap all over, just one example: https://openqa.opensuse.org/tests/318054#step/chromium/58
Updated by okurz almost 8 years ago
- Priority changed from Urgent to High
okurz wrote:
Also happens for Leap all over, just one example: https://openqa.opensuse.org/tests/318054#step/chromium/58
Yeah, ok. It's not "all over". It's only zdup-Leap-42.1-kde (latest) as it seems for Leap. Checking partitions and free space it seems like all scenarios use the same root partition size which is 16 GB. https://openqa.opensuse.org/tests/318054/file/textinfo-info.txt from the failing test shows /dev/vda2 16G 15G 446M 98% /
after the zdup and zdup-Leap-42.2-kde shows /dev/vda2 16G 11G 4.6G 70% /
so I assume this one has enough space for now but might run out if we have more submissions for 42.3 . Is there some data we can probably clean up like snapshots or should we create new images with more than 20G for /?
Updated by okurz almost 8 years ago
- Related to action #15242: update Leap 42.1->TW is running out of space added
Updated by michalnowak over 7 years ago
- Checklist item changed from to [x] DVD upgrade, [ ] zdup upgrade
Leap 42.1 Updated to Tumbleweed upgrade passed on gnome (https://openqa.opensuse.org/tests/334814) and kde (https://openqa.opensuse.org/tests/334753). zdup upgrade test suites may take some time till they are triggered by the whole update-this-and-than-that machinery.
Updated by michalnowak over 7 years ago
- Status changed from In Progress to Resolved
zdup: https://openqa.opensuse.org/tests/335624
This seems to me resolved.
Updated by michalnowak over 7 years ago
- Checklist item changed from to [x] zdup upgrade