action #55568

openQA Infrastructure - action #55178: ** PROBLEM Service Alert: openqa.suse.de/fs_/var/lib/openqa is WARNING **

action #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

Added by okurz 8 months ago. Updated 4 months ago.

Status:ResolvedStart date:15/08/2019
Priority:HighDue date:
Assignee:okurz% Done:

0%

Category:Bugs in existing tests
Target version:openQA Project - Current Sprint
Difficulty:
Duration:

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

History

#1 Updated by okurz 8 months 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

#2 Updated by okurz 8 months 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

#3 Updated by okurz 8 months ago

  • Copied to action #55571: [osd][staging][sle] Untracked assets that most likely should be tracked: SLE staging added

#4 Updated by okurz 8 months ago

  • Copied to deleted (action #55571: [osd][staging][sle] Untracked assets that most likely should be tracked: SLE staging)

#5 Updated by okurz 8 months ago

  • Assignee changed from runger to mloviska

@acotofana helped to find the responsible person, it's mloviska but we might need a vacation standin

#6 Updated by okurz 6 months 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.

#7 Updated by okurz 5 months ago

  • Status changed from New to Feedback
  • Assignee changed from mloviska to okurz
  • Target version set to Current Sprint

#8 Updated by okurz 4 months ago

  • Status changed from Feedback to Resolved

merged and done

Also available in: Atom PDF