action #65963
closed[sle][functional][u] performance issue of ppc64le workers on grenache
0%
Description
Observation¶
https://openqa.suse.de/tests/4147606#next_previous shows clearly the sporadic performance issue on workers.
grenache-1:22, grenache-1:26 fails still at bootloader
grenache-1:21 fails at scc_registration
grenache-1:25 fails at welcome
only couple of tests runs could not run successfully. This is configuration issue on grenache then. The better to solve this sporadic issue is reduce the amount of workers. With increase timeout in this case it won't help: SMS is not show up, it fails later at other test modules.
Suggestions¶
- check the configuration for workers like RAM, CPU
- reduce amount of workers to ensure that enough performance granted for automated testing
Updated by zluo about 4 years ago
- Related to action #65663: [sles][functional][u][sporadic] test fails in bootloader - lpar is not in "Not activate state" added
Updated by okurz about 4 years ago
Your repeated suggestion "The better to solve this sporadic issue is reduce the amount of workers" is not based on facts and also most likely not applicable here because the SUT is running on a different machine anyway. How should it help to e.g. disable some s390x controlling worker instances on grenache when the PVM machine instance "redcurrant" was executing the test? The recommendation regarding RAM assigned to the SUT might be helpful however then we would not test anymore the "minimum recommended" values so the test target would be something different.
Updated by SLindoMansilla almost 4 years ago
- Status changed from New to Rejected
- Assignee set to SLindoMansilla
- Target version set to Milestone 30
grenache was working fine during mentioned failures: https://openqa.suse.de/tests/4147646#step/scc_registration/8
It looks like a proxy SCC side problem.