action #55568
closedopenQA Infrastructure (public) - action #55178: ** PROBLEM Service Alert: openqa.suse.de/fs_/var/lib/openqa is WARNING **
openQA Tests (public) - coordination #55556: [epic][osd][functional][u] osd: Untracked assets that most likely should be tracked
[jeos][osd] Untracked assets that most likely should be tracked: JeOS
0%
Description
Observation¶
The space available on osd is limited. https://openqa.suse.de/admin/assets reveals some assets as "untracked" but probably they should be tracked by jobs, for example the following subset:
hdd/SLES15-SP2-JeOS.x86_64-15.2-VMware-Build2.8.vmdk.xz 147.94 MiB
hdd/SLES15-SP1-JeOS.x86_64-15.1-VMware-Build35.30.vmdk.xz 148.15 MiB
hdd/SLES15-JeOS.x86_64-15.0-XEN-Build25.1.qcow2 260.38 MiB
hdd/SLES15-JeOS.x86_64-15.0-MS-HyperV-Build25.1.vhdx 872 MiB
hdd/SLES15-JeOS.x86_64-15.0-kvm-and-xen-Build25.1.qcow2 260.38 MiB
hdd/SLES12-SP5-JeOS.x86_64-12.5-VMware-Build4.34.vmdk.xz 156.31 MiB
hdd/SLES12-SP4-JeOS.x86_64-12.4-VMware-Build10.30.vmdk 807.56 MiB
Updated by okurz over 5 years ago
- Subject changed from osd: Untracked assets that most likely should be tracked: JeOS to [jeos][osd] Untracked assets that most likely should be tracked: JeOS
Updated by okurz over 5 years ago
- Assignee set to runger
I can't find acotofana in the progress project, I will assign to @runger. I hope you are ok with that and can help to re-assign to the right person then
Updated by okurz over 5 years ago
- Copied to action #55571: [osd][staging][sle] Untracked assets that most likely should be tracked: SLE staging added
Updated by okurz over 5 years ago
- Copied to deleted (action #55571: [osd][staging][sle] Untracked assets that most likely should be tracked: SLE staging)
Updated by okurz over 5 years ago
- Assignee changed from runger to mloviska
@acotofana helped to find the responsible person, it's mloviska but we might need a vacation standin
Updated by okurz about 5 years ago
situation on osd unchanged. @mloviska would you be able to look into this? Should be as simple as referencing the needed JeOS assets in the test scenarios. If they are not needed consider moving the syncing and triggering to "OBS Sync", @andriinikitin can help, or do not even sync the assets or look into https://gitlab.suse.de/openqa/scripts/blob/master/rsync.pl#L245 which can provide a way to delete assets even after syncing.
Updated by okurz about 5 years ago
- Status changed from New to Feedback
- Assignee changed from mloviska to okurz
- Target version set to Current Sprint
doing it myself then: https://gitlab.suse.de/openqa/scripts/merge_requests/418
Updated by jlausuch almost 4 years ago
- Project changed from openQA Tests (public) to 208
- Category deleted (
Bugs in existing tests)
Updated by ph03nix about 2 months ago
- Project changed from 208 to Containers and images
- Target version deleted (
Current Sprint)