action #138512
closed[BCI] Reestablish the actual coverage of s390x and ppc64le
0%
Description
Basically, revert https://progress.opensuse.org/issues/138434 where we needed to reduce the coverage on s390x and ppc64le due to a reduced number of worker capacity during the datacenter migration.
Currently blocked until beginning of 2024, due to the ongoing datacenter move.
I set a due date to 31.01.2024 so that we don't forget about it.
Updated by ph03nix 8 months ago
- Related to action #138434: [BCI] Reduce load on s390x added
Updated by ph03nix 7 months ago
- Checklist item ppc64le added
- Checklist item s390x added
- Status changed from Blocked to Workable
We can re-enable ppc64le, see https://progress.opensuse.org/issues/138770#note-10
Updated by mgrossu 7 months ago
MR to re-enable ppc64le: https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/1413
Updated by okurz 5 months ago
- Related to action #154177: File systems alert Salt: One of the file systems is too full size:M added
Updated by mgrossu 5 months ago ยท Edited
MR to re-enable s390x: https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/1478
Updated by ph03nix 5 months ago
okurz wrote in #note-19:
Are you sure ppc64le tests are effective? Because the problem we saw some days ago was that BCI images are synced but never used on osd
Can you provide a bit more context or a link or something? We see the ppc64le jobs in OSD in the BCI job groups, and this is exactly what this ticket is about. I do not see any issues, what are we missing?
Updated by okurz 5 months ago
- Status changed from Feedback to Resolved
It seems it's ok. Jobs are running for newer builds so we can see in https://openqa.suse.de/admin/assets that according repositories are accounted for in the according job groups. There are some BCI build assets still "Untracked" for the older builds that did not schedule any jobs. Those assets will go away in some days. So all good now.