action #138512
closed
[BCI] Reestablish the actual coverage of s390x and ppc64le
Added by ph03nix 8 months ago.
Updated 5 months ago.
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.
- Subject changed from [BCI] Increase the coverage of s390x and ppc64le to [BCI] Reestablish the actual coverage of s390x and ppc64le
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Assignee deleted (
mgrossu)
- Status changed from Feedback to Workable
I think we can try to go back to the normal load on s390x as well.
- Priority changed from Normal to High
- Related to action #154177: File systems alert Salt: One of the file systems is too full size:M added
- Status changed from Workable to In Progress
- Assignee set to mgrossu
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Status changed from Resolved to Feedback
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
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?
- Priority changed from High to Normal
Lowering prio, as this ticket is ongoing for a long time.
- 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.
Also available in: Atom
PDF