QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Checked the SCC for SLES15SP4 LTSS: Release schedule: released Jan 01 2024
Will keep eyes on it and work on this ticket when SLES15SP4 LTSS is released on scc.

@zoecao we are working in parallel on this, can we agree on the renaming of the qcow images? I renamed the ones that have module names by adding ltss right after the last module:
'SLES-%HDDVERSION%-%ARCH%-GM-lp-contm-lgm-tsm-pcm-wsm-%DESKTOP%-all_patterns-updated.qcow2' --> 'SLES-%HDDVERSION%-%ARCH%-GM-lp-contm-lgm-tsm-pcm-wsm-ltss-%DESKTOP%-all_patterns-updated.qcow2'
and the ones that don't include any module names in the hdd name, I added ltss right after GM- :
'autoyast-SLES-%HDDVERSION%-%ARCH%-GM-%DESKTOP%-updated.qcow2' --> 'autoyast-SLES-%HDDVERSION%-%ARCH%-GM-ltss-%DESKTOP%-updated.qcow2'

for HA tests, I noticed that the 15SP3 tests don't include ltss in the naming, so I left it as is.
for SAP tests, the SP3 tests don't have ltss at all, not even in the SCC_ADDONS not sure how to proceed with this one.
WDYT?

syrianidou_sofia wrote in #note-7:

@zoecao we are working in parallel on this, can we agree on the renaming of the qcow images? I renamed the ones that have module names by adding ltss right after the last module:
'SLES-%HDDVERSION%-%ARCH%-GM-lp-contm-lgm-tsm-pcm-wsm-%DESKTOP%-all_patterns-updated.qcow2' --> 'SLES-%HDDVERSION%-%ARCH%-GM-lp-contm-lgm-tsm-pcm-wsm-ltss-%DESKTOP%-all_patterns-updated.qcow2'
and the ones that don't include any module names in the hdd name, I added ltss right after GM- :
'autoyast-SLES-%HDDVERSION%-%ARCH%-GM-%DESKTOP%-updated.qcow2' --> 'autoyast-SLES-%HDDVERSION%-%ARCH%-GM-ltss-%DESKTOP%-updated.qcow2'

The new names are good for me.

for HA tests, I noticed that the 15SP3 tests don't include ltss in the naming, so I left it as is.

Yes, it fine for me.

for SAP tests, the SP3 tests don't have ltss at all, not even in the SCC_ADDONS not sure how to proceed with this one.

Good question, there's no ltss for SAP, I just checked the product's lifecycle: https://www.suse.com/lifecycle/#suse-linux-enterprise-server-for-sap-applications-15, there's ESPOS (similar with LTSS), but it looks like ESPOS for SAP was not setup (https://scc.suse.com/admin/products/2136).
So my advise is to ask SAP product manager whether SAP15SP3/SP4 would go into ESPOS, if yes, product manager need to send request to SCC team to setup it. And Confirm with SAP product manager that we would test ESPOS for SAP migration or not (we once did this for hpc migration, similar with ltss, register it-> patch -> deregister it -> migration); if it won't go into ESPOS, may need to ask whether we test SAP15SP3 and SAP15SP4 migration scenarios.

@JERiveraMoya WDYT?

WDYT?

we have other tickets for renaming, but if you are going to rename something containing "ltss"", I would suggest to remove/drop this "ltss" from the name of the test suite, qcows2, etc.
It is a waste of time to be renaming things all the time, we should setup ltss in single place ideally or at least to minimize it.

OK, I will check the ticket of renaming testsuits and images and use the new name directly.

Submit a PR to add 'ltss' to sles15sp4 aotuyast profiles, I only add the profiles that installation via scc registration, because the media installation does not get ltss from "Full media".
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18373
VR: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20231226-2&groupid=251
The VRs are still running, will check the results tomorrow.

No problems with VRs:
VRs of creating support images: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20231226-3&groupid=251
VRs of migration case using the created images: https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao-20231227&distri=sle

So updated PR and submitted MR for this ticket:
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18373
MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/686

zoecao wrote in #note-12:

No problems with VRs:
VRs of creating support images: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20231226-3&groupid=251
VRs of migration case using the created images: https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao-20231227&distri=sle

No LTSS shown in the module list, so I think LTSS is still not ready for test. And for migration test, we need add ltss in the SCC_ADDONS.

So updated PR and submitted MR for this ticket:
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18373
MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/686

leli wrote in #note-13:

zoecao wrote in #note-12:

No problems with VRs:
VRs of creating support images: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20231226-3&groupid=251
VRs of migration case using the created images: https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao-20231227&distri=sle

No LTSS shown in the module list, so I think LTSS is still not ready for test. And for migration test, we need add ltss in the SCC_ADDONS.

Please take look at support images VRs, https://openqa.suse.de/tests/13158261#step/patch_sle/80, LTSS already could be registered. It didn't show in migration VR because it hasn't been enabled by rmt server, I can not run it with proxySCC jobs either, but images works fine to boot and perform migration, Sofia's ticket would take care of migration settings.

So updated PR and submitted MR for this ticket:
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18373
MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/686

zoecao wrote in #note-14:

leli wrote in #note-13:

zoecao wrote in #note-12:

No problems with VRs:
VRs of creating support images: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20231226-3&groupid=251
VRs of migration case using the created images: https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao-20231227&distri=sle

No LTSS shown in the module list, so I think LTSS is still not ready for test. And for migration test, we need add ltss in the SCC_ADDONS.

Please take look at support images VRs, https://openqa.suse.de/tests/13158261#step/patch_sle/80, LTSS already could be registered. It didn't show in migration VR because it hasn't been enabled by rmt server, I can not run it with proxySCC jobs either, but images works fine to boot and perform migration, Sofia's ticket would take care of migration settings.

Ok, this proved 15SP4 LTSS already ready on SCC.

So updated PR and submitted MR for this ticket:
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18373
MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/686