action #99246
closedPublished QCOW images appear to be uncompressed
Description
QCOW images generated by OpenQA install jobs appear to be uncompressed now.
ppc64le: https://openqa.suse.de/tests/7211627#downloads
HDD_1: 885MB
PUBLISH_HDD_1: 7.1GB
x86_64: https://openqa.suse.de/tests/7211569#downloads
HDD_1: 976MB
PUBLISH_HDD_1: 4.2GB
The size difference should be only a few hundred megabytes at most.
Updated by okurz about 3 years ago
- Category set to Regressions/Crashes
- Priority changed from Normal to Urgent
- Target version set to Ready
Treating as "urgent" assuming it's a recent regression
Updated by okurz about 3 years ago
Updated by okurz about 3 years ago
osukup had an idea: https://github.com/os-autoinst/os-autoinst/pull/1783
Updated by okurz about 3 years ago
- Status changed from New to In Progress
- Assignee set to okurz
osukup created the PR, thanks a lot for that. I tested the PR locally and merged. Packages are building. Triggered a new deployment but it might fail because packages in https://build.opensuse.org/project/monitor/devel:openQA?arch_x86_64=1&blocked=1&broken=1&building=1&defaults=0&deleting=1&dispatching=1&failed=1&finished=1&locked=1&repo_openSUSE_Leap_15_2=1&scheduled=1&signing=1&succeeded=1&unresolvable=1 are not yet done building. Anyone can monitor https://gitlab.suse.de/openqa/osd-deployment/-/pipelines/216149 and retrigger in case the pipeline did not wait long enough.
Updated by osukup about 3 years ago
tested locally on quasar.suse.cz
SLE-15-SP2-Installer-DVD-x86_64-GM-DVD1.iso (9.9 GiB)
SLES-15-SP2-x86_64-minimal_installed_for_LTP.qcow2 (976 MiB) <- base image
SLES-15-SP2-x86_64-minimal_installed_for_LTP-uefi-vars.qcow2 (does not exist)
sle-15-SP2-x86_64-5.3.18-344.1.g7d43568-Server-DVD-Incidents-Kernel-KOTD@64bit-with-ltp.qcow2 (1.6 GiB) < generated new qcow2 with compresion
Updated by openqa_review about 3 years ago
- Due date set to 2021-10-09
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz about 3 years ago
- Status changed from In Progress to Feedback
- Priority changed from Urgent to High
Current situation looks good. We have the fix available, merged, deployed to OSD as well. Thanks a lot to everybody that helped. Thx to osukup for the quick fix. I would like to keep the ticket open to find further points for improvement, e.g. how to increase test coverage, monitoring, process, etc.
EDIT: 2021-09-27
- Looking at https://monitor.qa.suse.de/d/WebuiDb/webui-summary?viewPanel=47&orgId=1&from=1626435701542&to=1632687629034 it looks indeed like in 2021-07 the Disk I/O times were significantly lower than in 2021-08
- In late 2021-08 and 2021-09 there were multiple Disk I/O related alerts but no relevant followup was conducted. This for me another reminder that we should dilligently act on alerts and try really hard to understand the reasons for any failing.
Updated by okurz about 3 years ago
- Copied to coordination #99579: [epic][retro] Follow-up to "Published QCOW images appear to be uncompressed" added
Updated by okurz about 3 years ago
- Status changed from Feedback to Resolved
Created #99579 as a proper follow-up
Updated by okurz about 3 years ago
- Related to coordination #96447: [epic] Failed systemd services and job age alerts added
Updated by openqa_review about 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/7554138
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review about 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/7618901
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review about 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/7656193
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234