action #153808
Updated by szarate 4 months ago
## Observation
To avoid bugs like https://bugzilla.suse.com/show_bug.cgi?id=1218923 where a test configuration error creates a problem, it is better to diagnose during first_boot and boot_to_desktop
In general, we should be able to read on either module if the system's RAM is under `< 4GB` and `DESKTOP=gnome` or `DESKTOP=minimal` and let the reviewers know of the situation.
If it's `first_boot` we need to add the fatal flag; if it's `boot_to_desktop`, soft_fail explaining the reason, or adding a record_info (fail), so it clearly shows that it is something off/wrong, without affecting the overall result of the test suite.
Take into account the possibility of overriding hardware requirements (https://documentation.suse.com/sles/15-SP5/single-html/SLES-deployment/#sec-x86-requirements)
### Acceptance Criteria
- Ensure Machine type ppc64le-2g also has a 4g counterpart
- The `first_boot` module fails if memory requirements are not met unless explicitly asked (i.e. via variable)
- The `boot_to_desktop` module records an error or soft fails if memory requirements aren't met
openQA test in scenario sle-15-SP5-Online-QR-SAP-ppc64le-create_hdd_sles4sap_gnome@ppc64le-2g fails in
[first_boot](https://openqa.suse.de/tests/13272276/modules/first_boot/steps/10)
## Test suite description
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
## Reproducible
Fails since (at least) Build [134.1](https://openqa.suse.de/tests/13272276) (current job)
## Expected result
Last good: [134.1](https://openqa.suse.de/tests/13270278) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online-QR-SAP&machine=ppc64le-2g&test=create_hdd_sles4sap_gnome&version=15-SP5)