Project

General

Profile

Actions

action #66358

open

[qe-sap][sles4sap] Tests specified with machine 2G but the test specifies 32G . This is not the way tests are intended to run and multiple jobs incomplete

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

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-05-03
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

See for example https://openqa.suse.de/tests/4186410 incompleting on powerqaworker-qam-1 or https://openqa.suse.de/tests/4186470 on QA-Power8-5-kvm . These tests are unlikely to work in a stable way. Please use "machines" in openQA properly and do not specify a custom value of memory on test suites. And I suggest to use dedicated machines to allocate this much amount of RAM as currently we can not scale up that easily.

Actions #1

Updated by ldevulder over 4 years ago

I will create a MACHINE entry for this.

We don't have the possibility to use dedicated servers yet, mainly because we don't have Power8 servers. We are trying to have Power9 servers that we could dedicated for these "big" SAP tests, but a lot of work will be needed to adapt current KVM tests on PowerVM...

Actions #2

Updated by okurz over 3 years ago

  • Subject changed from [qa-css][sles4sap] Tests specified with machine 2G but the test specifies 32G . This is not the way tests are intended to run and multiple jobs incomplete to [qa-css][sles4sap][asg] Tests specified with machine 2G but the test specifies 32G . This is not the way tests are intended to run and multiple jobs incomplete
Actions #3

Updated by okurz about 3 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

Actions #4

Updated by jctmichel about 3 years ago

  • Subject changed from [qa-css][sles4sap][asg] Tests specified with machine 2G but the test specifies 32G . This is not the way tests are intended to run and multiple jobs incomplete to [qe-sap][sles4sap] Tests specified with machine 2G but the test specifies 32G . This is not the way tests are intended to run and multiple jobs incomplete
Actions #5

Updated by jctmichel about 3 years ago

We are waiting for our new hardware to arrive in Prague (expected sometime in November 2021). This hardware is intended for the openQA hardware pool and will allow us to create very large VMs in order to test large HANA scenarios, freeing up other resources within the openQA pool, but also (and I must be cautious here...) possibly available for other non-SAP-specific SLES tests that might require huge VMs.

I believe there are some Power9 machines in openQA at the moment. These machines should be sufficient to provide very large VMs (~512GB RAM). Is this something we could consider and take advantage of?

Actions #6

Updated by jctmichel about 3 years ago

  • Status changed from New to In Progress
Actions #7

Updated by okurz almost 3 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days).

Actions #8

Updated by szarate over 2 years ago

These tickets are not on high prio

Actions #9

Updated by szarate over 2 years ago

  • Tags set to bulkupdate

These tickets are not on high pro

Actions #10

Updated by szarate over 2 years ago

  • Priority changed from High to Normal
Actions #11

Updated by slo-gin 8 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF