openSUSE Release Process

I was cloning it with HANA=nfs://1c119.qa.suse.de/srv/nfs/sap/HANA2/51055297.bsc1195133 to make it pass.
Looks like https://bugzilla.suse.com/show_bug.cgi?id=1195133#c36 is not really fixed ?
See https://suse.slack.com/archives/C02CU8X53RC/p1657275288084449

Kind of interesting this only comes up now. Where were the past HANA install fails reported on 15 SP4? FCS was a while ago.

Anyway, it is to be expected since SAP HANA is not even supported on 15 SP4 yet, so it should not actually pass anyway until SAP approve. AP adds new OS's to the HANA installer, so the OS version can be checked. I'm not sure how the team deals with that so far, e.g. when testing new products the OS version check is ignored. If this isn't documented anywhere for QE-SAP, then now seems a good time. So once HANA is supported on SP4, then we'll need to get that version for SP4 testing. In the new tests we'll have multiple HANA versions in use depending on SLE SP; I'm not sure how that is handled today.

The information about SAP HANA support is at: https://launchpad.support.sap.com/#/notes/2235581
And there is an old index to such information sources at: https://wiki.suse.net/index.php?title=SAP_Links

LMartin wrote:

Kind of interesting this only comes up now. Where were the past HANA install fails reported on 15 SP4? FCS was a while ago.

It seems 15-SP4 build validation was using nfs://1c119.qa.suse.de/srv/nfs/sap/HANA2/51055297.bsc1195133 (see: https://openqa.suse.de/tests/8752361#settings)

While the QAM job is configured with nfs://1c119.qa.suse.de/srv/nfs/sap/HANA2/SPS05rev57/%ARCH% (see: https://gitlab.suse.de/qa-css/openqa_ha_sap/-/blob/master/openQA/yaml_job_groups/maintenance/maintenance_sle15_sp4_sap.yml#L160)

I would say the 15-SP4 QAM job was configured based on the values used in 15-SP3 QAM: https://gitlab.suse.de/qa-css/openqa_ha_sap/-/blob/master/openQA/yaml_job_groups/maintenance/maintenance_sle15_sp3_sap.yml#L160

ok, I checked with LinuxLab. It seems the HANA installer no longer checks the OS version it is installing on, so I was wrong, HANA should not by definition fail to install.
--> means we actually need to investigate the issues found by @Ednilson Miura and @Jozef Pupava.
my error.